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-12-26] Reports - After deleting saved search, column settings on Expenses tab are not reset #77829
Version Number: 9.2.79-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:#77673 Email or phone of affected tester (no customers):hjidjnfjsdiuhs@gmail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Mac 26.1 / Chrome App Component: Search
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Create an expense.
Go to Reports > Reports.
Click Columns.
Unselect all the options except Action > Save.
Click Filters.
Click Save search.
Click 3-dot menu on the saved search > Delete > Delete it.
Expected Result:
After deleting saved search and redirecting to Expenses tab, column settings on Expenses tab should reset to default.
Actual Result:
After deleting saved search and redirecting to Expenses tab, column settings from the saved search are applied to Expenses tab.
👋 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 [-]Reports - After deleting saved search, column settings on Expenses tab are not reset[/-][+][Due for payment 2025-12-26] Reports - After deleting saved search, column settings on Expenses tab are not reset[/+]on Dec 19, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.84-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@luacmartins / @JS00001@trjExpensify 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 Dec 17, 2025
Triggered auto assignment to @trjExpensify (
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 Dec 17, 2025
Triggered auto assignment to @danieldoglas (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Dec 17, 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 Dec 17, 2025
💬 A slack conversation has been started in #expensify-open-source
trjExpensify commentedon Dec 17, 2025
CC: @luacmartins @JS00001 @brunovjk @QichenZhu
4 remaining items
m-natarajan commentedon Dec 17, 2025
Not Repro in Ad-hoc build
Screen.Recording.2025-12-17.at.23.13.16.mp4
IuliiaHerets commentedon Dec 18, 2025
Issue is not reproducible on Windows 11 / Chrome in v9.2.81-4
bandicam.2025-12-18.13-49-42-249.mp4
luacmartins commentedon Dec 18, 2025
Fixed
[-]Reports - After deleting saved search, column settings on Expenses tab are not reset[/-][+][Due for payment 2025-12-26] Reports - After deleting saved search, column settings on Expenses tab are not reset[/+]melvin-bot commentedon Dec 19, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 19, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.84-8 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-12-26. 🎊
melvin-bot commentedon Dec 19, 2025
@luacmartins / @JS00001 @trjExpensify 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]