Reports - Move expense button is missing when there is open report in the workspace

[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.20-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #71319
Email or phone of affected tester (no customers): djsnoisjosiso@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Account has no workspace.

1. Go to staging.new.expensify.com
2. Create two workspaces.
3. Delete the workspace that has Default label.
4. Go to workspace chat.
5. Create an expense in workspace chat.
6. Create a new report via + > Create report (optional).
7. Go to Reports > Expenses.
8. Select the expense via checkbox.
9. Click dropdown button.

Expected Result:

Move expense button will be shown because there is open report in the workspace.

Actual Result:

Move expense button is missing when there is open report in the workspace.

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

Bug6959935_1759191630133.Screen_Recording_2025-09-30_at_08.17.24.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @sonialiap (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 @srikarparsi (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[melvin-bot]

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

[koko57]

I am the author of the offending PR, I will handle this

[srikarparsi]

Which PR was it by the way @koko57?