[Due for payment 2025-04-28] Expense - Report field in paid expense shows that another report is selected

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.1.28-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): sdjdsdsmoijs@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Delayed submissions and Add approvals are enabled in Workflows settings.

1. Go to staging.new.expensify.com
2. Create a new workspace.
3. Go to workspace chat.
4. Submit an expense to the workspace chat.
5. Click Submit button.
6. Submit another expense.
7. Click Submit, Approve and then Pay elsewhere.
8. Go to transaction thread of the paid expense in Step 7.
9. Click Report.
10. Note that the selected report is not the same report where the paid expense is located. It is the submitted report in Step 5.
11. Click on the selected report.
12. Click on the expense preview.
13. Note that the transaction thread is empty.
14. Click on the report subtitle to go back to previous page.
15. Click on the expense preview.
16. Click Report.
17. Click on the selected report.
18. Repeat Step 16 and 17.
19. Now the transaction thread is empty again with skeleton header.

Expected Result:

In Step 10, the selected report should be the report that the paid expense is located in.

Actual Result:

In Step 10, the selected report is not the same report where the paid expense is located. It is the submitted report in Step 5.
When trying to move the paid expense to the submitted report in Step 13 and 19, the transaction thread is empty.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6802317_1744687759771.20250415_112246.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @garrettmknight

[melvin-bot]

Triggered auto assignment to @garrettmknight (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @madmax330 (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[madmax330]

@Guccio163 @mountiny could this be related to: #60174