[$250] Reports - Move expense is not present when the track expense is moved to a report in Reports

[lanitochka17]

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.64-2
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #63683
Email or phone of affected tester (no customers): sdjoisdnjsoidjsos@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

• Account has self DM

1. Go to staging.new.expensify.com
2. Create a workspace
3. Go to self DM
4. Track a manual expense in self DM
5. Click Submit it to someone
6. Select the workspace chat
7. Enter merchant and click Create expense
8. In workspace chat, create an empty report
9. Go to Reports > Reports
10. Select the reported track expense via checkbox
11. Click dropdown button
12. Move expense option is present
13. Go to self DM
14. Track a manual expense with merchant in self DM
15. Go to Reports > Expenses
16. Select the unreported track expense via checkbox
17. Click dropdown button > Move expense
18. Select any open report
19. Go to Reports > Reports
20. Select the new reported track expense from Step 16 to 18) via checkbox
21. Click dropdown button

Expected Result:

Move expense should be present when the track expense is moved to a report in Reports, as there are open reports

Actual Result:

Move expense is not present when the track expense is moved to a report in Reports

Workaround:

Unknonw

Platforms:

Select the officially supported platforms where the issue was reproduced:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Platforms Tested:

On which of our officially supported platforms was this issue tested:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6857107_1749656578919.20250611_233732.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021933139168929307573
• Upwork Job ID: 1933139168929307573
• Last Price Increase: 2025-06-26

Issue Owner

Current Issue Owner: @ishpaul777

[melvin-bot]

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

[BlameGPT]

Possible culprit PRs for this issue

• Fix condition to report unreported transactions #63683: The PR test steps and title directly address moving unreported transactions to reports and verifying the 'Move expense' option is available in the Reports page dropdown, matching the issue reproduction flow.
• fix: remove Move expense from the secondary action menu #63616: This PR explicitly removes the 'Move expense' option from a secondary action menu, which could cause the 'Move expense' option to be missing as described in the issue.
• Report-Report is not shown in WS chat online after trying to move it to deleted WS offline #63433: This PR involves moving reports between workspaces and handling report display after move attempts, which relates to report and expense movement flows relevant to the issue.

[Julesssss]

Hey @luacmartins, i think this is another related to moving expenses but it seems demoteable to me.

[JS00001]

This looks like an old issue that we can demote, its related to this:

App/src/libs/ReportActionsUtils.ts

Line 139 in bc49778

function isDeletedAction(reportAction: OnyxInputOrEntry<ReportAction | OptimisticIOUReportAction>): boolean {

, where we are returning true instead of false for it being deleted