[Change Policy] Expense - Every field on expense report is displayed empty after changing expense to other WS

[jponikarchuk]

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?: N/A - new feature, doesn't exist in prod
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: N/A
Email or phone of affected tester (no customers): ibellicotest+286@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome
App Component: Money Requests

Action Performed:

Prerequisite: User should have at least two workspaces created.

1. Open the Expensify app.
2. Open any worksapce.
3. Tap on the "+" button and select "Create Expense"
4. Complete the creation flow.
5. Once redirected to chat, open the expense report.
6. Tap on header and select "Share"
7. Copy expense URL.
8. Return to expense report.
9. Paste the URL and add /change-workspace to it.
10. Send the link and tap on it.
11. Select a different workspace to move the expense to.
12. Once redirected to report again, check how are all the fields on the report, displayed after this action.

Expected Result:

All the information in the expense report fields, should still be visible after moving the expense to a different workspace.

Actual Result:

All the fields on expense report are displayed empty after moving the expense to a different workspace.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6770316_1741926836556.Empty.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @luacmartins

[melvin-bot]

Triggered auto assignment to @mollfpr (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @lydiabarclay (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]

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

[rayane-d]

I think this is not a blocker, given that this feature is currently only accessible via URL. However, it is definitely a bug we should fix.

[mollfpr]

I agree with @rayane-d 👍