[Due for payment 2026-05-12] [$250] Reports - Unable to open expense after applying "Limit Results" filter.

[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.3.60-6
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: #86297
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Search

Action Performed:

1. Open the staging.new.expensify.com website.
2. Sign up with a new account.
3. Complete onboarding selecting "Track and budget expenses" option.
4. Navigate to workspace chat.
5. Create a manual expense but don´t open report.
6. Navigate to "Reports" > "Expenses"
7. Click on "Display" > "Limit Results"
8. Set the limit to "1" and apply it.
9. Once redirected to results, note that "Status" field on just created expense is displayed empty.
10. Try to open the expense report.
11. Note that no action is triggered.
12. Click on "Display" > "Limit Results" > "Reset"
13. Open and close the expense report.
14. Click on "Display" > "Limit Results" one more time.
15. Set the limit to "1" again and apply it.
16. Note that now, status on expense preview is visible and report can be opened.

Expected Result:

After applying the "Limit Results" filter, user should be able to open the expenses on results, and preview of expenses should correctly display the status.

Actual Result:

After applying the "Limit Results" filter, expense displayed on results can´t be opened and "Status" field is displayed empty. This issue reproduces if expense report wasn´t opened before.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7131572_1776358749791.Limit.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022045146411595858458
• Upwork Job ID: 2045146411595858458
• Last Price Increase: 2026-04-24
• Automatic offers:
• aimane-chnaif | Reviewer | 111248499

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

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

[melvin-bot]

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

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

[OSBotify]

Investigation Summary: Classification: Frontend bug. Causing PR: #86297 - Revamp Search page actions bar by @bernhardoj (High confidence). Recommendation: REVERT. PR 86297 revamped the Search page actions bar and moved the Limit Results control from a separate RHP route into an inline DisplayPopup dropdown. The regression is directly tied to this refactoring -- the bug is staging-only, affects a new feature introduced by this PR, and the melvin-bot auto-assigned the PR author based on this PR. Assigned: @bernhardoj (PR author), @aimane-chnaif @JS00001 @luacmartins (approving reviewers). Labels: No label changes -- DeployBlockerCash is appropriate for this frontend bug. Root Cause: The PR moved the Limit Results control out of a dedicated RHP screen into an inline DisplayPopup. When applyChanges is called in TextInputPopup, updateFilterForm reads the current searchAdvancedFilters Onyx value synchronously -- if the form has not been populated yet (expense report was never opened, so no prior filter sync has run), the query string built from that snapshot is missing fields like status. The result is an incomplete query URL, so search results have empty status values and cannot be opened. After the user manually opens the report, Onyx state gets populated and the second attempt works correctly, matching the described workaround. Files verified: src/components/Search/FilterDropdowns/DisplayPopup.tsx, src/hooks/useAdvancedSearchFilters.ts, src/hooks/useSearchFilterSync.ts.