Skip to content

[Due for payment 2025-08-15] Search does not respect RHP-applied filters on the Reports > Expenses view #67923

Closed

Description

@m-natarajan

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


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:

  1. Navigate to Reports > Expenses page > Advanced filters
  2. Select a filter (e.g., Billable: Yes)
  3. Click save
  4. 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 evidence
Recording.1480.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @alexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 5, 2025
  2. melvin-bot commented on Aug 5, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on Aug 5, 2025

    @melvin-bot

    Triggered auto assignment to @Julesssss (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. github-actions commented on Aug 5, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. melvin-bot commented on Aug 5, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  6. assigned and unassigned on Aug 5, 2025
  7. Julesssss commented on Aug 5, 2025

    @Julesssss
    Contributor

    Hey @JS00001, I see you tookover here. Do you know the cause?

  8. JS00001 commented on Aug 5, 2025

    @JS00001
    Contributor

    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

  9. Julesssss commented on Aug 5, 2025

    @Julesssss
    Contributor

    Nice, thanks

  10. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Aug 8, 2025
  11. 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
  12. melvin-bot commented on Aug 8, 2025

    @melvin-bot

    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. 🎊

  13. melvin-bot commented on Aug 8, 2025

    @melvin-bot

    @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]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions