You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-10-15] Expense - Confirm page is missing receipt placeholder when reviewing duplicates #71944
Version Number: 9.2.24-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail:#69875 Email or phone of affected tester (no customers):sjdjoisjnoisjsodoi@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Create two expenses with the same amount in workspace chat.
Open the expense report.
Open transaction thread (IMPORTANT).
Click Review duplicates.
Click Keep this one on any expense.
Select details (if prompted) and reach the confirm page.
Expected Result:
Confirm page will show receipt placeholder.
Actual Result:
Confirm page does not show receipt placeholder.
This issue happens with and without receipt.
This issue also happens on the confirm page when merging expenses.
👋 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:
Identify the pull request that introduced this issue and revert it.
👋 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:
Identify the pull request that introduced this issue and revert it.
changed the title [-]Expense - Confirm page is missing receipt placeholder when reviewing duplicates[/-][+][Due for payment 2025-10-15] Expense - Confirm page is missing receipt placeholder when reviewing duplicates[/+]on Oct 8, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.27-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@parasharrajat@NicMendonca The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Oct 7, 2025
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 commentedon Oct 7, 2025
Triggered auto assignment to @MarioExpensify (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 7, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 7, 2025
👋 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:
14 remaining items
github-actions commentedon Oct 7, 2025
👋 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:
melvin-bot commentedon Oct 7, 2025
💬 A slack conversation has been started in #expensify-open-source
mountiny commentedon Oct 8, 2025
Fixed in prod, no need for payment
[-]Expense - Confirm page is missing receipt placeholder when reviewing duplicates[/-][+][Due for payment 2025-10-15] Expense - Confirm page is missing receipt placeholder when reviewing duplicates[/+]melvin-bot commentedon Oct 8, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.27-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-10-15. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Oct 8, 2025
@parasharrajat @NicMendonca The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]