Reports-Search query does not update when click on week group header

[mitarachim]

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.3.11-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: #80684
Email or phone of affected tester (no customers): ndk.2303+224@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 11 Home/Chrome
App Component: Search

Action Performed:

1. Open https://staging.new.expensify.com/
2. Navigate to Reports > Expense
3. Enter in the Search box field: 'groupBy:week'
4. Click on a week group header (e.g., "Jan 25 - Jan 31, 2026")

Expected Result:

Verify the search query updates to filter by that week's date range
Verify groupBy is removed from the query
Verify only transactions from that week are displayed as individual items (not grouped)

Actual Result:

The search query does not update, the group only collapses instead.
Failed Test 10 in PR

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7060828_1769656443529.80684-Search_Query_Is_Not_Updated.mp4

Bug7060828_1769656336595.search_quey_is_not_updated_when_click_on_the_list_header.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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