[Due for payment 2025-03-28] [Change Policy] Expense - Deleted expense can still be moved to a different workspace.

[IuliiaHerets]

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
Email or phone of affected tester (no customers): ibellicotest+298@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: Have at least two workspaces available.

1. Open the staging.new.expensify.com website.
2. Open any workspace chat.
3. Create an expense.
4. Open the expense report.
5. Tap on the header and select "Share"
6. Copy the URL.
7. Return to report and paste the URL.
8. At the end of it, add /change-workspace
9. Tap on header again and delete the expense.
10. Return to LHN and open the expense report thread.
11. Tap on the URL and select any workspace to send the expense.
12. Check if the expense is sent to another workspace.

Expected Result:

User shouldn´t be able to send a deleted expense to a different workspace.

Actual Result:

User is able to move an already deleted expense to a different workspace when navigating to the "change-workspace" URL.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6770424_1741937983987.Move_Deleted.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @slafortune

[melvin-bot]

Triggered auto assignment to @slafortune (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 @youssef-lr (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.

[hungvu193]

Looks like from this one: #57553

cc @rayane-d