Report - After moving expense to a report on WS, system message, shows incorrect report name

[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.65-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: N/A
Email or phone of affected tester (no customers): ibellicotest+1031@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome (mWeb - Hybrid App) / Windows 10 - Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace created.
Prerequisite 2: Account has a Self DM.

1. Open the Expensify app.
2. Open any workspace chat.
3. Submit a manual expense to it.
4. Navigate to Self DM and submit a manual track expense to it.
5. Open the expense created on Self DM.
6. Tap on the report field and select the report of the expense created on workspace chat.
7. Once navigated to report, open the just moved expense.
8. Note that system message generated shows "Moved this expense to Receipt missing details" instead of report number.
9. Add a merchant and category to expense.
10. Note that now, system message displays expense amount instead of report number.

Expected Result:

System message generated when moving an expense from Self DM to a report on a workspace, should display the correct number of name of the report.

Actual Result:

System message generated when moving an expense from Self DM to a report, shows "Moved this expense to Receipt missing details" instead of report number, and after adding a merchant and category, it only shows the expense amount instead of report name or number.

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

Bug6857607_1749695258668.Incorrect.mp4

View all open jobs on GitHub

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

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]

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

[melvin-bot]

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