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-16] [Due for payment 2025-06-16] [Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report #63505
Version Number: 9.1.59-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: Exp Email or phone of affected tester (no customers):sdjonsjdosdjodi@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.4 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Submit two expenses to the workspace chat.
Click on the expense preview.
Select all expenses via checkbox.
Click on the report header subtitle to return to workspace chat.
On workspace chat, click + > Create report.
Submit two more expenses to the new report.
Click on the new report from Step 7.
Expected Result:
Selection mode will not persist in the new report.
Actual Result:
Selection mode from the other report persists in the new 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.
Add check when adding expenses #63171: This PR changes components related to adding expenses and report previews, which are part of the flow involving opening reports and could affect selection state.
changed the title [-][Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/-][+][Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/+]on Jun 6, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.60-2-staging and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@DylanDylann@greg-schroeder@DylanDylann 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]
changed the title [-][Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/-][+][Due for payment 2025-06-16] [Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/+]on Jun 9, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.61-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@DylanDylann@greg-schroeder@DylanDylann 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]
changed the title [-][Due for payment 2025-06-16] [Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/-][+][Due for payment 2025-06-16] [Due for payment 2025-06-16] [Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/+]on Jun 9, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.62-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@DylanDylann@greg-schroeder@DylanDylann 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 Jun 4, 2025
Triggered auto assignment to @greg-schroeder (
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 Jun 4, 2025
Triggered auto assignment to @marcaaron (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Jun 4, 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 Jun 4, 2025
💬 A slack conversation has been started in #expensify-open-source
BlameGPT commentedon Jun 5, 2025
Possible culprit PRs for this issue
MonilBhavsar commentedon Jun 5, 2025
Commented on the suspicious code https://github.com/Expensify/App/pull/62472/files#r2128392466
22 remaining items
[-][Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/-][+][Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/+]melvin-bot commentedon Jun 6, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.60-2-staging 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-13. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jun 6, 2025
@DylanDylann @greg-schroeder @DylanDylann 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]
[-][Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/-][+][Due for payment 2025-06-16] [Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/+]melvin-bot commentedon Jun 9, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.61-0 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-16. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jun 9, 2025
@DylanDylann @greg-schroeder @DylanDylann 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]
[-][Due for payment 2025-06-16] [Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/-][+][Due for payment 2025-06-16] [Due for payment 2025-06-16] [Due for payment 2025-06-13] [Due for payment 2025-06-12] Expense - Selection mode from the previous report is not cleared when opening another report[/+]melvin-bot commentedon Jun 9, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.62-0 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-16. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jun 9, 2025
@DylanDylann @greg-schroeder @DylanDylann 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]