You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-10-14] Expense - Description row does not expand and long description is truncated in split details #102484
Version Number: 9.4.95-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#101301 Email or phone of affected tester (no customers):jsdoijnodsdisojo@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.5 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Open 1:1 DM with any user.
Create a split expense with description containing more than 2 lines.
Open the split preview.
Expected Result:
Description row will be expanded and show the full description.
Actual Result:
Description row does not expand and long description is truncated in split details page.
👋 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:
Identify the pull request that introduced this issue and revert it.
Root cause: That PR turned on the new dropdown-row layout for the manual confirmation list, including the read-only split details page. In that layout, a read-only description now renders through ExpenseFieldRow with numberOfLinesValue={2} (DescriptionField.tsx:110-120). This is a plain <Text numberOfLines={2}>, so the text gets cut off.
Recommended fix (roll forward): In DescriptionField.tsx, render the read-only description as HTML with no line limit. Pick one:
Option A (matches production): always use the MenuItemWithTopDescription branch (lines 122-136) for the read-only description.
Option B (keeps the new look): pass ExpenseFieldRow a valueComponent that renders <RenderHTML> of the parsed comment, and drop the 2-line limit.
If neither fix lands before the deploy, revert the PR.
Investigation details
Why production shows the full text: production uses MenuItemWithTopDescription with shouldParseTitle. A parsed title goes through <RenderHTML>, which ignores numberOfLinesTitle (MenuItem.tsx:994-1009). The old numberOfLinesTitle={2} never took effect. Copying it to the new row made the limit real for the first time.
How the split page gets the new layout:DynamicSplitBillDetailsPage renders MoneyRequestConfirmationList with isReadOnly. useAddReceiptLayout.tsx:30 sets shouldUseDropdownRows: true whether or not the page is read-only.
Likely second regression (found in the code, not tested): the new row doesn't parse markdown. Links, mentions and formatting in split descriptions would show as raw text. Option A or B fixes this too. Only lowering the line limit (numberOfLinesValue={0}) would not.
Other checklist PRs ruled out:Split MoneyRequestConfirmationList restructured the confirmation list but didn't touch DescriptionField or the dropdown-row layout.
Activity
applause-bot commentedon Sep 29, 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/df21ded7bfa101d8f6d9951ea6bf34a40b7d2cbce799c4fce48a7ad06166a167
melvin-bot commentedon Sep 29, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #101301
melvin-bot commentedon Sep 29, 2026
@puneetlath @ikevin127 you have been assigned to this deploy blocker because you reviewed the offending PR: #101301
melvin-bot commentedon Sep 29, 2026
@thelullabyy you have been assigned to this deploy blocker because you authored the offending PR: #101301
github-actions commentedon Sep 29, 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 29, 2026
💬 A slack conversation has been started in #expensify-open-source
MelvinBot commentedon Sep 29, 2026
Deploy Blocker Analysis
Causing PR: [CFI] Update the Manual create expense form to use dropdown-style rows and a compact add-receipt button (high confidence). The auto-assignment is correct.
Root cause: That PR turned on the new dropdown-row layout for the manual confirmation list, including the read-only split details page. In that layout, a read-only description now renders through
ExpenseFieldRowwithnumberOfLinesValue={2}(DescriptionField.tsx:110-120). This is a plain<Text numberOfLines={2}>, so the text gets cut off.Recommended fix (roll forward): In
DescriptionField.tsx, render the read-only description as HTML with no line limit. Pick one:MenuItemWithTopDescriptionbranch (lines 122-136) for the read-only description.ExpenseFieldRowavalueComponentthat renders<RenderHTML>of the parsed comment, and drop the 2-line limit.If neither fix lands before the deploy, revert the PR.
Investigation details
MenuItemWithTopDescriptionwithshouldParseTitle. A parsed title goes through<RenderHTML>, which ignoresnumberOfLinesTitle(MenuItem.tsx:994-1009). The oldnumberOfLinesTitle={2}never took effect. Copying it to the new row made the limit real for the first time.DynamicSplitBillDetailsPagerendersMoneyRequestConfirmationListwithisReadOnly. useAddReceiptLayout.tsx:30 setsshouldUseDropdownRows: truewhether or not the page is read-only.numberOfLinesValue={0}) would not.DescriptionFieldor the dropdown-row layout.view run
22 remaining items
melvin-bot commentedon Oct 13, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Oct 13, 2026
Payment Summary
Resolving PRs:
Expense - Description row issue in split bill flow #102796
Reviewer: @ikevin127 owed $175 via NewDot
Reviewer: @thelullabyy owed $175 via NewDot
BugZero Checklist (@mallenexpensify)
ikevin127 commentedon Oct 16, 2026
Note
No payment due here as this was a regression follow-up from the main issue.
melvin-bot commentedon Oct 16, 2026
Current assignee @mallenexpensify is eligible for the Awaiting Payment assigner, not assigning anyone new.