Skip to content

[Due for payment 2026-10-14] Expense - Description row does not expand and long description is truncated in split details #102484

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


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:

  1. Go to staging.new.expensify.com
  2. Open 1:1 DM with any user.
  3. Create a split expense with description containing more than 2 lines.
  4. 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.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7272000_1790633544331.7.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7272000

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. applause-bot commented on Sep 29, 2026

    @applause-bot
    Author

    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

  2. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 29, 2026
  3. melvin-bot commented on Sep 29, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #101301

  4. melvin-bot commented on Sep 29, 2026

    @melvin-bot

    @puneetlath @ikevin127 you have been assigned to this deploy blocker because you reviewed the offending PR: #101301

  5. melvin-bot commented on Sep 29, 2026

    @melvin-bot

    @thelullabyy you have been assigned to this deploy blocker because you authored the offending PR: #101301

  6. github-actions commented on Sep 29, 2026

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  7. melvin-bot commented on Sep 29, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  8. MelvinBot commented on Sep 29, 2026

    @MelvinBot
    Contributor

    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 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.

    view run

  9. 22 remaining items

  10. melvin-bot commented on Oct 13, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  11. melvin-bot commented on Oct 13, 2026

    @melvin-bot

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  12. ikevin127 commented on Oct 16, 2026

    @ikevin127
    Contributor

    Note

    No payment due here as this was a regression follow-up from the main issue.

  13. added and removed
    Awaiting PaymentAuto-added when associated PR is deployed to production
    on Oct 16, 2026
  14. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Oct 16, 2026
  15. melvin-bot commented on Oct 16, 2026

    @melvin-bot

    Current assignee @mallenexpensify is eligible for the Awaiting Payment assigner, not assigning anyone new.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions