[$250] Reports - New search is reset to type:expense when previous search was performed in Filters

[lanitochka17]

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.2.86-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #75828
Email or phone of affected tester (no customers): sdhsiudhsiuhdsib@gmail.co
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Search

Action Performed:

1. Go to staging.new.expensify.com
2. Go to Reports > Reports.
3. Click Filters.
4. Click Keywords.
5. Write anything and click Save.
6. Click View results.
7. Click on the search result.
8. Type anything and search.

Expected Result:

App should continue the search with type:expense-report and replace only keyword search.

Actual Result:

New search is reset to type:expense when previous search was performed in Filters.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7036074_1766499599335.22.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022005615860743030685
• Upwork Job ID: 2005615860743030685
• Last Price Increase: 2025-12-29

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @JmillsExpensify

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #75828

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @bfitzexpensify (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.

[github-actions]

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

[TaduJR]

Assignment here @JS00001

[TaduJR]

Was able to repo on prod. I think it's not regression from #75828

@situchan Are you also able to repo on prod?