[Due for payment 2025-11-17] Expense - Confirm modal shows "Delete expenses" when deleting the report

[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.2.15-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: #70111
Email or phone of affected tester (no customers): dsjionsjosdijdso@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create two expenses in the workspace chat.
4. Open the expense report.
5. Click More > Delete.

Expected Result:

The confirm modal will show "Delete report".

Actual Result:

The confirm modal shows "Delete expenses", which does not sound correct because the expenses are not deleted and they will move to self DM when deleting the entire report.

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

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @CortneyOfstad

[melvin-bot]

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

[MarioExpensify]

@zirgulis @mollfpr @alitoshmatov I believe this is a regression from #70111

Can you guys take a look please?

[MarioExpensify]

@nyomanjyotisa I appreciate the proposal but we should follow up on the original PR before looking for other proposed solutions.

[alitoshmatov]

Yes looks like it is from our PR, @MarioExpensify please assign me. @zirgulis Can you create follow up PR?