[Due for payment 2026-06-04] [Due for payment 2026-06-03] Spend - Dropdown button shows Mark as done, but report row shows Submit

[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.83-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #88455
Email or phone of affected tester (no customers): sjiodjosdjnonsjdoni2@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• User A and User B completed onboarding with Track expenses for my business intent.
• User A invites User B to the workspace.
• Perform steps below as User B.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense.
4. Go to Spend > Reports.
5. Select the expense via checkbox.
6. Click dropdown button.

Expected Result:

Dropdown button will show the same button as the report row.

Actual Result:

Dropdown button shows Mark as done, but report row shows Submit.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7163827_1779830884692.5.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7163827

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/809ac1b59325f1d87dcdbdf341de98d6d030bce8f37f8a496cae7adcbe5ba2de

[melvin-bot]

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

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

[MelvinBot]

Proposal

What is the root cause of that problem?

The DeferredActionCell component renders a placeholder button while useDeferredValue resolves. This placeholder at DeferredActionCell.tsx:16-19 always uses actionTranslationsMap[action] to determine the button text — which maps SUBMIT → "Submit" — without checking shouldShowMarkAsDone.

The full ActionCell does have the shouldShowMarkAsDone check and would show "Done", but it only renders after the deferred transition completes. In the virtualized Spend > Reports list, components frequently mount/unmount during scrolling, so users see the placeholder "Submit" text.

Meanwhile, the dropdown (via MoneyReportHeaderSelectionDropdown) and the report header button (via SubmitPrimaryAction) call shouldShowMarkAsDone directly without a deferred wrapper, so they correctly show "Mark as done".

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

Add the shouldShowMarkAsDone check to the DeferredActionCell placeholder rendering path in DeferredActionCell.tsx. When action is SUBMIT and the track-intent conditions are met, the placeholder text should show "Done" (matching what ActionCell shows) instead of "Submit".

This requires passing the report/policy data needed for the shouldShowMarkAsDone check through to DeferredActionCell, mirroring how ActionCell already receives and uses it.

What alternative solutions did you explore?

An alternative would be to remove the deferred rendering entirely for SUBMIT actions in track-intent contexts, but that would hurt scroll performance. The proposed fix is minimal — it only changes the placeholder text logic.

---

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.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[IuliiaHerets]

Chrome / v9.3.83-1
Passed

bandicam.2026-05-27.13-41-13-248.mp4