[$250] Expense - To field shows wrong workspace after creating new report on confirm page

[applause-bot]

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.64-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: #87962
Email or phone of affected tester (no customers): sjiodjnsoijdnijsiojosj1@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Create two workspaces - A and B.
3. Create an empty report in each workspace chat.
4. Open FAB > Create expense > Manual.
5. Enter amount > Next.
6. On confirm page, click Report field.
7. Select report from workspace B.
8. Click Report field.
   → Create report button subtitle shows workspace A.
9. Click Create report.
10. Click Report field.
    → The new report is created in workspace A.
11. Click RHP back button.
    → To field shows workspace B, when the selected report in Step 10 is from workspace A.

Expected Result:

To field should update to workspace A because the selected report in Report field is workspace A.

Actual Result:

To field shows workspace B when the selected report in Report field is workspace A.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7140146_1777381054308.11.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022051932123994388588
• Upwork Job ID: 2051932123994388588
• Last Price Increase: 2026-05-06

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

📣 @applause-bot[bot]! 📣
Please report bugs or suggest features in the #expensify-open-source Slack channel, don't directly open issues in this repo!
Instructions here to join the channel 📖

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

[MelvinBot]

Proposal

What is the root cause of that problem?

PR #87962 (fixing #87441) changed the "Create report" button to use the default workspace for the user's own expenses. However, when createReportForPolicy creates a new report, it routes through handleRegularReportSelection, which only updates transaction.reportID but does not update transaction.participants.

The "To" field on the confirmation page is derived from transaction.participants. So after creating a report in workspace A, reportID points to workspace A but participants still references workspace B — causing the stale "To" field.

By contrast, handleGlobalCreateReport correctly updates both reportID and participants when selecting a report.

What changes do you think we should make in order to solve the problem?

Update handleRegularReportSelection in IOURequestStepReport.tsx to also pass updated participants (with the new report's policyID and reportID) to setTransactionReport, matching the pattern used by handleGlobalCreateReport. This ensures the "To" field stays in sync whenever the report changes.

What alternative solutions did you explore? (Optional)

An alternative would be to add a useEffect in IOURequestStepConfirmation that syncs participants whenever transaction.reportID changes (similar to the existing PAY-type sync at line 210). However, updating at the source (handleRegularReportSelection) is cleaner and avoids reactive cascading updates.

Investigation details

Data flow of the bug:

1. User is on confirm page with expense targeting workspace B (transaction.participants has policyID=B)
2. User opens Report field, clicks "Create report"
3. Because this is the user's own expense, targetExpensePolicyID is set to undefined
4. usePolicyForMovingExpenses falls back to the active/default workspace (A)
5. createReportForPolicy creates a report in workspace A, then calls handleRegularReportSelection
6. handleRegularReportSelection calls setTransactionReport with only {reportID: newReportID} — no participants update
7. Back on confirmation page: transaction.reportID → workspace A, but transaction.participants → still workspace B
8. "To" field renders stale workspace B

Related issue: #87441 (the original issue that PR #87962 was fixing)

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.