[Change Policy] Expense - Able to choose to move report from invited to owner workspace but moving fails

[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.13-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
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): applausetester+im0d11@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• User is invited to a workspace.
• User created their own workspace.

1. Go to staging.new.expensify.com
2. Go to the invited workspace chat.
3. Submit an expense.
4. Click Submit.
5. Go to expense report.
6. Add /change-workspace to the end of the URL and navigate to the link.
7. Select your own workspace.

Expected Result:

If the submitted report cannot be moved from the invited workspace to another workspace where the submitter is the admin, the workspace should not appear in the list when moving report.

Actual Result:

All the workspaces arre in the list when moving report from the invited workspace. When moving the submitting report from the invited workspace to another workspace where the submitter is the admin, the report cannot be moved.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6770434_1741939056108.20250314_155012.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @rayane-d

[melvin-bot]

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