Per diem - Report from other workspace is missing in report list when moving per diem expense

[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.3.7-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-3292/folder/13176670/45748766/1143584175
Email or phone of affected tester (no customers): sodinjsondjosndsoi@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Create two workspaces - A and B.
• Workspace A has per diem rates.
• Do not enable Per diem feature for Workspace B.

1. Go to staging.new.expensify.com
2. Go to workspace chat B.
3. Create an empty report.
4. Go to workspace chat A.
5. Create a per diem expense.
6. Open the per diem expense.
7. Click Report field.

Expected Result:

Empty report from workspace B should appear in the report list (production behavior).

Actual Result:

Empty report from workspace B does not appear in the report list.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

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

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #79415 - "Fix report field is enabled when there are no outstanding reports" by @bernhardoj (High confidence)
Related Issues: #78788 (original issue that PR 79415 fixed)

Recommendation: REVERT

PR #79415 should be reverted. While it successfully fixed the original issue (#78788), it introduced a regression that prevents users from seeing reports from other workspaces when moving per diem expenses.

Labels: Keeping DeployBlockerCash (this is a Frontend/App bug that blocks the App deploy)

📋 Detailed Analysis

Evidence

1. Issue is staging-only: Bug is reproducible on staging 9.3.7-1 but NOT in production
2. PR timeline matches: PR Fix report field is enabled when there are no outstanding reports #79415 was merged on 2026-01-22 at 16:03 UTC and is included in the staging deploy checklist
3. PR modifies exact affected code: The PR changes IOURequestStepReport.tsx (the report selection flow for expenses)
4. Bug symptoms match the code changes: The PR added logic to pass selectedPolicyID for per diem transactions, which restricts the report list

Verification

• Affected file: src/pages/iou/request/step/IOURequestStepReport.tsx (modified by PR Fix report field is enabled when there are no outstanding reports #79415)
• Key hook: src/hooks/useOutstandingReports.ts (created by PR Fix report field is enabled when there are no outstanding reports #79415)
• The PR modifies the report filtering logic that determines which reports appear in the list

Root Cause

PR #79415 introduced a new hook useOutstandingReports and changed how selectedPolicyID is passed when selecting a report for per diem expenses.

The problematic change is in IOURequestStepReport.tsx lines 238-243:

let selectedPolicyID;
if (isPerDiemTransaction) {
    selectedPolicyID = perDiemOriginalPolicy?.id;
} else {
    selectedPolicyID = !isEditing && !isFromGlobalCreate ? reportOrDraftReport?.policyID : undefined;
}

When a user creates a per diem expense in Workspace A and tries to move it by clicking the Report field, selectedPolicyID is set to Workspace A's policy ID. This causes useOutstandingReports to only return reports from Workspace A (lines 45 of the hook), filtering out reports from Workspace B.

The intended behavior: When moving a per diem expense, users should be able to see reports from ALL workspaces (including empty reports from other workspaces), not just reports from the workspace where the per diem was created.

Trade-off: Reverting will reintroduce issue #78788 (report field being clickable when there are no outstanding reports), but that is a less severe UX issue than completely hiding valid destination reports.