[Due for payment 2025-09-22] [$250] Reports -"It´s not here" page displayed when merging expenses from different WS on "Reports"

[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.2.9-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 TestRail: #68204
Email or phone of affected tester (no customers): ibellicotest+1769@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb) - Windows 11 / Chrome
App Component: Search

Action Performed:

Prerequisite: Account has at least two workspaces available.

1. Open the staging.new.expensify.com website.
2. Open any workspace chat.
3. Create a manual expense.
4. Navigate to another workspace chat.
5. Create a different manual expense.
6. Navigate to "Reports"
7. Open the last created expense.
8. Tap on "More" and select "Merge"
9. Select the first created expense to merge with.
10. Tap on "Continue"
11. Select the amount and report of the first created expense.
12. Tap on "Continue" and confirm the expenses merge.
13. Note that you are redirected to a "It´s not here" page.

Expected Result:

When merging two expenses, user should automatically land on report again, with the updated amount and information.

Actual Result:

When merging expenses from different workspaces on "Reports" user is redirected to a "It´s not here" page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6941007_1757547375656.Here.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021966275211321936640
• Upwork Job ID: 1966275211321936640
• Last Price Increase: 2025-09-11

Issue Owner

Current Issue Owner: @dylanexpensify

[melvin-bot]

Triggered auto assignment to @dylanexpensify (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 @Gonals (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.

[francoisl]

cc @youssef-lr @hoangzinh