[Due for payment 2026-02-03] Expense - Create report button shows wrong workspace, expense cannot be moved

[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.3.8-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: #76000
Email or phone of affected tester (no customers): sdjoisdnjodinjsodjidsji1@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition-

• Admin has two workspaces - A and B.
• Workspace A is default workspace.
• Admin invites member to workspace B.

1. Go to staging.new.expensify.com
2. [Member] Go to the invited workspace chat.
3. [Member] Create an expense.
4. [Admin] Open member's expense report.
5. [Admin] Click Report > Create report.

Expected Result:

Create report button will show workspace B as the subtitle.

Actual Result:

Create report button shows workspace A as the subtitle. As a result, the expense cannot be moved to a new report.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7056840_1769217104761.8.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @heyjennahay

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

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