[Due for payment 2026-08-19] Report - "This expense was put on hold" is not completelly visible on report preview.

[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.52-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: #97005
Email or phone of affected tester (no customers): ibellicotest+2766@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.

1. Open the staging.new.expensify.com website.
2. Open any workspace chat.
3. Create a manual expense.
4. Right click on preview > "Hold"
5. Enter any reason and hold the expense,
6. Note that "This expense was put on hold" message on report preview, is displayed on the same line as date and category and is not completelly visible.

Expected Result:

"This expense was put on hold" message on report preview, should be displayed on a different line as date and category, and should be completelly visible.

Actual Result:

"This expense was put on hold" message on report preview, is displayed on the same line as date and category and is not completelly visible as it doesn´t fit inside preview.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7230934_1786449658488.Hold_Cut.1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7230934

Issue Owner

Current Issue Owner: @Krishna2323

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/17f3d1861dee61ad50bbce952a33f1a567907007367f931bdebfee688246dbff

[melvin-bot]

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

[melvin-bot]

@JS00001 @JmillsExpensify @ShridharGoel you have been assigned to this deploy blocker because you reviewed the offending PR: #97005

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

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