Unreported per diem expense cannot be duplicated on Inbox, but can be duplicated on Reports

[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.3.58-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #84657
Email or phone of affected tester (no customers): iojnsdiojoisjnosnjido@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Search

Action Performed:

Precondition:

• Workspace has per diem rates.

1.Go to staging.new.expensify.com
2. Go to self DM.
3. Create a per diem expense.
4. Open the expense.
5. Click More > Duplicate.
→ Unreported per diem expense cannot be duplicated on Inbox.
6. Go to Reports > Expenses.
7. Select the unreported per diem expense via checkbox.
8. Click dropdown button > Duplicate expense.
→ Unreported per diem expense can be duplicated on Reports.

Expected Result:

Unreported per diem expense should not be allowed to be duplicated on Reports, similar to Step 5 on Inbox.

Actual Result:

Unreported per diem expense cannot be duplicated on Inbox, but can be duplicated on Reports.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7126611_1775816485890.2.mp4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #84657

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