[Due for payment 2026-03-02] Expense - "You rejected this report" appears in report after admin reopens 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.3.21-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: https://test-management.browserstack.com/projects/2219752/test-runs/TR-5545/folder/13176741/41237125/1196512676
Email or phone of affected tester (no customers): sjiondjsondjoisjsojdos@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:

Precondition:

• Disable Approvals and Payments in Workflows.
• Admin invites member to the workspace.

1. Go to staging.new.expensify.com
2. [Member] Go to workspace chat.
3. [Member] Create an expense.
4. [Member] Click Submit on the expense preview.
5. [Admin] Open member's expense report.
6. [Admin] Click More > Retract.
7. [Admin] Close and reopen the report.

Expected Result:

"You rejected this report" will not appear in the expense report after admin reopens report.

Actual Result:

"You rejected this report" appears in bold in the expense report after admin reopens report.

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

Issue Owner

Current Issue Owner: @NicMendonca

[melvin-bot]

Triggered auto assignment to @NicMendonca (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 @cristipaval (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: Needs Investigation
Causing PR: Unable to determine with high confidence
Reproducibility: Staging only (not on production)

Recommendation: NEEDS INVESTIGATION

The bug involves incorrect report state display after reopening a retracted report. After reviewing the StagingDeployCash PRs, I could not identify a clear causing PR that modifies the retract/reject/reopen functionality in the current staging deploy (v9.3.21-0).

Key Findings

1. Bug Symptoms: After admin retracts a report and reopens it, the message "You rejected this report" appears instead of the expected message. This suggests potential confusion between RETRACTED and REJECTED action types.

2. Related Code: The display logic in src/libs/ReportNameUtils.ts (function computeReportNameBasedOnReportAction) handles both REJECTED and RETRACTED actions separately:

   • Line 404: REJECTED → shows "rejected this report"
   • Line 407: RETRACTED → shows "retracted"
   • Line 410: REOPENED → shows "reopened"

3. Relevant PR (Not in Staging): PR fix: New expense is not added to the retracted report #81237 "fix: New expense is not added to the retracted report" modified the reopenReport function in src/libs/actions/IOU/index.ts but was merged on Feb 6 and is NOT in the current staging deploy.

4. PRs Reviewed: Checked all PRs in the staging deploy checklist including performance optimization PRs ([No QA] perf: optimize accessing report summaries #82545, [No QA] perf: replace reportsSelector with useReportAttributes hook #82551, perf: add useMappedPolicies hook #82563) and context splitting PR (Split contexts to state and actions - Batch 2 #81986), but none directly modify retract/reject/reopen logic.

Possible Root Causes

1. Backend Issue: The API might be returning the wrong action type (REJECTED instead of RETRACTED) after reopening
2. State Management Issue: Report state might not be correctly updated after the reopen operation
3. Display Logic Issue: The logic determining which message to show might be using stale or incorrect data

Next Steps

1. Need to verify with backend team if there were any recent API changes to the reopen/retract endpoints
2. Tag PR authors of recent report-related changes for input
3. Check if this is a data issue specific to certain workspace configurations

@jponikarchuk Could you provide more details:

• What is the exact message that appears? Is it showing in the report header, expense preview, or elsewhere?
• Does this happen for all retracted reports or only under specific conditions (e.g., specific workspace settings)?
• Are there any console errors when reproducing the issue?

Labels: No label changes made - keeping both blocker labels until root cause is identified with high confidence.