Repository navigation
Task - Description with morethan 100 characters is not truncated. #102618
Description
If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.
Version Number: V9.4.97-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #102170
Email or phone of affected tester (no customers): dreamnitethedragon+vegst@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redmi note 10s android 13
App Component: Chat Report View
Action Performed:
- Launch the app
- Open a chat
- Create a task with a description having formatted text more than 100 characters
- Open the task details and check the Description row
Expected Result:
Description with more than 100 characters must be truncated with "..." in the description row.
Actual Result:
Description with more than 100 characters is displayed in full without truncation.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome Safari
Screenshots/Videos
Bug7273113_1790738046408.Screenrecorder-2026-09-30-08-39-15-297.mp4
Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7273113
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
applause-bot commentedon Sep 30, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/024fd005427b791afb2521bbfb801c368f686a20ca4dbc44d6825d0c25046b78
melvin-bot commentedon Sep 30, 2026
@roryabraham recently merged #102170, but they are OOO right now, so I'll auto-assign someone else.
github-actions commentedon Sep 30, 2026
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Sep 30, 2026
Triggered auto assignment to @MonilBhavsar (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Sep 30, 2026
@roryabraham @Pujan92 you have been assigned to this deploy blocker because you reviewed the offending PR: #102170
melvin-bot commentedon Sep 30, 2026
@war-in you have been assigned to this deploy blocker because you authored the offending PR: #102170
melvin-bot commentedon Sep 30, 2026
💬 A slack conversation has been started in #expensify-open-source
[-]Task-Description with morethan 100 characters is not truncated.[/-][+]Task - Description with morethan 100 characters is not truncated.[/+]MelvinBot commentedon Sep 30, 2026
Deploy Blocker Analysis
Verdict: Not a regression. I recommend removing
DeployBlockerCash. Task descriptions have never been truncated, in production or staging.Why the tester expected truncation: QA step 3 of
MenuItemdecomposition - html value says: "Create the task, open a room > Details > Description, set a description longer than 100 characters… verify that the row shows the formatted text truncated". The 100-character check applies to the room description. The step starts with "Create the task", so the tester checked the task's Description row instead.Recommendation: Remove the blocker label and close this as expected behavior. If product wants task descriptions truncated, file that as a new feature request.
Evidence
shouldRenderAsHTMLandnumberOfLinesTitle={0}, with no character limit. Staging: TaskView.tsx:251-265. Production: TaskView.tsx:252-265. No PR in Deploy Checklist: New Expensify 2026-09-30 touchesTaskView.tsx.numberOfLinesTitlehas no effect there (MenuItem.tsx:1006-1009). The new version (DynamicNewTaskPage.tsx:222-226) behaves the same way.characterLimit={100}at DynamicReportDetailsPage.tsx:1092. That row appears only whenisChatRoomis true (line 283), so it never appears for tasks. The truncation logic in MenuItemFieldValueHTML.tsx:31-33 looks correct.Next Steps: Optionally,
war-incould split QA step 3 of the PR into two steps so the room check and the task check are clearly separate. Reply with@MelvinBot <your feedback>to refine this analysis.view run
Pujan92 commentedon Sep 30, 2026
@jponikarchuk is it truncated in production?Seems like the test step needs to be corrected, as I don't see the truncation in prod either. @war-in
roryabraham commentedon Sep 30, 2026
I'm OOO and won't be able to help with this deploy blocker
war-in commentedon Sep 30, 2026
100% right, sorry for missing
notin the test step. I think we can close this