[Due for payment 2026-06-17] [$250] Expense - CMD+B opens wrong workspace after moving report to another workspace

[applause-bot]

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.4.0-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 BrowserStack: #92064
Email or phone of affected tester (no customers): jsodjosnjdodjsojsio@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:

Precondition:-

• Have two workspaces - A and B.

1. Go to staging.new.expensify.com
2. Go to workspace chat A.
3. Create an expense.
4. Open the expense.
5. Click More > Change workspace.
6. Select workspace B.
7. Press CMD+B.

Expected Result:

Workspace B settings will open because the currently opened report is from Workspace B.

Actual Result:

Workspace A settings opens after moving expense to report from Workspace B and the currently opened report is from Workspace B.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7172974_1780689399370.19.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Nathan Lemma
Bug ID: 7172974

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022064006636821127310
• Upwork Job ID: 2064006636821127310
• Last Price Increase: 2026-06-08

Issue Owner

Current Issue Owner: @rojiphil

[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/19ee64e971e92bb90e3c1118ded66f03ec097b1327a710a0f2521c441018634c

[melvin-bot]

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

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

[godzillaxbox19982014-lgtm]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Expense - CMD+B opens wrong workspace after moving report to another workspace

What is the root cause of that problem?

I traced this to the path that handles workspace name, expense report, CMD:

• src/libs/actions/IOU/SplitTransactionUpdate.ts:751 (workspaceExpenseReportID): const workspaceExpenseReportID = isConfirmedWorkspaceTransaction ? (workspaceChatReport?.iouReportID ?? splitTransaction?.reportID) : undefined;
• src/libs/actions/IOU/SplitTransactionUpdate.ts:754 (iouReportID): const iouReportID = workspaceExpenseReportID ?? splitExpense?.reportID ?? transactionThreadReport?.parentReportID;
• src/libs/actions/IOU/SplitTransactionUpdate.ts:757 (newTransactionReportID): const newTransactionReportID = isSelfDMPerDiemSplit ? CONST.REPORT.UNREPORTED_REPORT_ID : (workspaceExpenseReportID ?? splitExpense?.reportID);
• The local evidence matches this recurring failure shape: optimistic transaction/report data is written to one Onyx key but the visible list reads another derived key. Here, src/libs/actions/IOU/SplitTransactionUpdate.ts:751 and src/libs/actions/IOU/SplitTransactionUpdate.ts:754 do not agree on the same workspace name, expense report, CMD value, so the user-visible path can show a missing or stale state even though nearby data already has the needed context.

What changes do you think we should make in order to solve the problem?

• Update src/libs/actions/IOU/SplitTransactionUpdate.ts:751 to derive workspace name, expense report, CMD from the report/transaction source that owns this flow before the value is consumed.
• Carry the same normalized value through src/libs/actions/IOU/SplitTransactionUpdate.ts:754; that follows the safer family move to align optimistic/success/failure data with the selector consumed by the screen, so the write/optimistic/read paths agree instead of only changing the visible component.
• Keep the change inside the Reports, Expenses, IOU, Transactions surface and avoid changing payment actions, personal/deleted policies.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

1. Add or update a regression in tests/unit/ReportUtils*.ts for the exact issue flow: Expense - CMD+B opens wrong workspace after moving report to another workspace.
2. Cover the counter-case near src/libs/actions/IOU/SplitTransactionUpdate.ts:751 so valid existing workspace name, expense report, CMD behavior still works.
3. Manually repeat the issue steps after the patch and confirm the visible state/action is no longer stale.

What alternative solutions did you explore? (Optional)

• I would not add a broad new condition outside these referenced paths; the safer fix is to keep workspace name, expense report, CMD consistent at the first read/write boundary shown above.

[MelvinBot]

Proposal

Please re-state the problem that we are trying to solve in this issue.

After moving an expense to Workspace B, pressing CMD+B while viewing that expense opens Workspace A's settings instead of Workspace B's. Reproduced on web (dev) — confirmed the bug is in the new shortcut handler, not in the move flow.

What is the root cause of that problem?

The CMD+B handler resolves the workspace from Navigation.getTopmostReportId():

GoToWorkspaceHandler.tsx:23-29

But getTopmostReportId() → getTopmostReportParams.ts:22-39 only looks for SCREENS.REPORT routes inside REPORTS_SPLIT_NAVIGATOR (the central pane).

An expense report is opened at /e/<reportID>, which is the SEARCH_MONEY_REQUEST_REPORT screen — a Super Wide RHP route (ROUTES.ts:879), not a central-pane report. So getTopmostReportId() skips the visible expense report and returns the underlying chat's reportID — the original Workspace A chat. The handler then reads Workspace A's policyID.

The move itself works correctly: Onyx confirmed the expense report's policyID was updated to Workspace B. The shortcut just reads the wrong report.

This is actually broader than "moving workspace" — any time an expense report from one workspace is opened on top of a chat belonging to a different workspace, CMD+B opens the underlying chat's workspace. The move just creates that A-vs-B divergence.

Runtime evidence (web reproduction)

• Expense report 3254934021648211, Onyx policyID = 06431C809B4F108E (Workspace B) ✅ move persisted correctly.
• URL while viewing: /e/3254934021648211 (Super Wide RHP) — reportID unchanged before/after the move.
• CMD+B navigated to /workspaces/FE2CDF0E2572586E/overview = Workspace A ❌.
• FE2CDF0E2572586E is the underlying Workspace A chat's policyID, returned because the expense report lives in the RHP, invisible to getTopmostReportId().

What changes do you think we should make in order to solve the problem?

In GoToWorkspaceHandler.tsx, prefer the topmost Super Wide RHP report (the expense report on screen) before falling back to the central-pane report. There's already a helper for this: Navigation.getTopmostSuperWideRHPReportID().

const reportID = Navigation.getTopmostSuperWideRHPReportID() ?? Navigation.getTopmostReportId();

This makes CMD+B resolve the policy of the expense report actually being viewed (Workspace B), while preserving existing behavior when no expense report is open.

What alternative solutions did you explore?

None needed — the existing helper covers the RHP case. Note there are sibling CMD+B deploy blockers from the same PR #92064 worth checking together, since they share the "wrong/stale topmost report" theme:

• Web - Workspace - CMD+B opens not here page for archived #admins room or workspace chat #92813
• Web - Room - CMD+B opens not here page for invited room #92815
• [Due for payment 2026-06-17] Web - Spend - CMD+B is no longer responsive after pressing it once on Spend > Reports #92825

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/92830) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.