[Change Policy] Expense - System message created when changing expense´s WS, disappears when reacting to it.

[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?: No
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+296@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 available.

1. Open the Expensify app.
2. Open any workspace chat.
3. Create an expense.
4. Open the just created expense report.
5. Tap on the header and select "Share"
6. Copy the expense URL.
7. Return to report.
8. Paste the URL and add /change-workspace to it.
9. Send the link and tap on it.
10. Select any workspace to move the expense to.
11. Navigate to the workspace where the expense was moved to.
12. Open the expense report.
13. Long tap on the system message generated when the expense was moved.
14. Add any reaction to the message.
15. Check the system message behaviour when a reaction is added to it.

Expected Result:

System message should remain visible after a reaction is added to it.

Actual Result:

System message generated when an expense is moved to a different workspace, disappears after reacting to it.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6770343_1741929426077.React.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @luacmartins

[melvin-bot]

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