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-06-12] [Due for payment 2025-05-27] Expense - "Review duplicates" button is unresponsive on expenses report. #61973
Version Number: 9.1.45-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: N/A Email or phone of affected tester (no customers):ibellicotest+725@gmail.com Issue reported by: Applause Internal Team Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome App Component: Money Requests
Action Performed:
Open the Expensify app.
Open any workspace chat.
Submit two similar expenses.
Open the expenses report.
Tap on "Review Duplicates" on top of the report.
Note that no action is triggered with this action.
Expected Result:
When tapping on "Review Duplicates" on expenses report, the user should be able to begin the process to resolve the duplicates.
Actual Result:
"Review Duplicates" button is unresponsive on expenses report.
👋 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.
The linked PR was reverted and the steps in the OP already catched this bug, so I don't think we need regression test for this one. Feel free to close.
changed the title [-][Due for payment 2025-05-27] Expense - "Review duplicates" button is unresponsive on expenses report.[/-][+][Due for payment 2025-06-12] [Due for payment 2025-05-27] Expense - "Review duplicates" button is unresponsive on expenses report.[/+]on Jun 5, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.59-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@hungvu193@lydiabarclay@hungvu193 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 May 14, 2025
Triggered auto assignment to @lydiabarclay (
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 May 14, 2025
Triggered auto assignment to @mollfpr (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 14, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 14, 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:
mollfpr commentedon May 14, 2025
This is a regression from #60292
cc @VickyStash @hungvu193
31 remaining items
melvin-bot commentedon May 27, 2025
Payment Summary
Upwork Job
BugZero Checklist (@lydiabarclay)
lydiabarclay commentedon May 27, 2025
hungvu193 commentedon May 28, 2025
The linked PR was reverted and the steps in the OP already catched this bug, so I don't think we need regression test for this one. Feel free to close.
[-][Due for payment 2025-05-27] Expense - "Review duplicates" button is unresponsive on expenses report.[/-][+][Due for payment 2025-06-12] [Due for payment 2025-05-27] Expense - "Review duplicates" button is unresponsive on expenses report.[/+]melvin-bot commentedon Jun 5, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jun 5, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.59-7 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-06-12. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jun 5, 2025
@hungvu193 @lydiabarclay @hungvu193 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]