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-08-15] Search does not respect RHP-applied filters on the Reports > Expenses view #67923
Version Number: 9.1.89-3 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@JS00001 Slack conversation (hyperlinked to channel name): #Expensify Bugs
Action Performed:
Navigate to Reports > Expenses page > Advanced filters
Select a filter (e.g., Billable: Yes)
Click save
Click view results
Expected Result:
The search should return results that match the search term AND the applied filter (e.g., only expenses that are billable).
Actual Result:
The search ignores the applied filter and returns results from the unfiltered dataset.
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceRecording.1480.mp4
👋 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 [-]Search does not respect RHP-applied filters on the Reports > Expenses view[/-][+][Due for payment 2025-08-15] Search does not respect RHP-applied filters on the Reports > Expenses view[/+]on Aug 8, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.90-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@JS00001@alexpensify 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 Aug 5, 2025
Triggered auto assignment to @alexpensify (
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 Aug 5, 2025
Triggered auto assignment to @Julesssss (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Aug 5, 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 Aug 5, 2025
💬 A slack conversation has been started in #expensify-open-source
Julesssss commentedon Aug 5, 2025
Hey @JS00001, I see you tookover here. Do you know the cause?
JS00001 commentedon Aug 5, 2025
Yes it was #67295. I reverted it for now, and its been CPd and the bug no longer exists on staging. Going to close this
Julesssss commentedon Aug 5, 2025
Nice, thanks
[-]Search does not respect RHP-applied filters on the Reports > Expenses view[/-][+][Due for payment 2025-08-15] Search does not respect RHP-applied filters on the Reports > Expenses view[/+]melvin-bot commentedon Aug 8, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.90-11 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-08-15. 🎊
melvin-bot commentedon Aug 8, 2025
@JS00001 @alexpensify 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]