Reports - Unable to reset sort order on display dropdown.

[jponikarchuk]

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-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: #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. Navigate to "Reports" > "Expenses"
3. Click on the "Display" dropdown button.
4. Click on "Sort By" > "Sort Order"
5. Note that sort order is set to "Descending"
6. Click on "Ascending" > "Apply"
7. Click on "Display" > "Sort By" > "Sort Order" again.
8. Click on "Reset"
9. Click on "DIsplat" > "Sort By" > "Sort Order" one more time.
10. Note that sort order is still "Ascending" and wasn´t resetted.

Expected Result:

"Sort order" in "Display" dropdown button should return to default after clicking on "Reset"

Actual Result:

"Sort Order" in "Display" dropdwon button doesn´t return to default after clicking on "Reset"

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

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

[MelvinBot]

Proposal

What is the root cause of that problem?

The SortOrderPopup passes the wrong defaultValue to SingleSelectPopup. At SortOrderPopup.tsx:42, the default is set to sortOrderOptions.at(0)?.value, which evaluates to 'asc' because CONST.SEARCH.SORT_ORDER defines ASC before DESC. However, the parser's actual default sort order is 'desc' (searchParser.peggy:65).

When Reset is clicked, SingleSelectPopup.resetChanges() restores the value to this incorrect defaultValue of 'asc' instead of 'desc'.

What changes do you think we should make in order to solve the problem?

Change the defaultValue in SortOrderPopup.tsx from sortOrderOptions.at(0)?.value to CONST.SEARCH.SORT_ORDER.DESC so that Reset restores the sort order to the parser's actual default of descending.

What alternative solutions did you explore? (Optional)

An alternative would be to reorder the keys in CONST.SEARCH.SORT_ORDER to put DESC first, but that's fragile — the default should be explicitly stated rather than depending on object key order.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[OSBotify]

Investigation Summary: Frontend bug. Causing PR: 86297 (Revamp search page actions bar by @bernhardoj, High confidence). Recommendation: REVERT. PR 86297 introduced SortOrderPopup.tsx with an incorrect defaultValue - it passes sortOrderOptions.at(0)?.value which resolves to asc (first element of [asc, desc]), but the actual app default is CONST.SEARCH.SORT_ORDER.DESC (desc per SearchUIUtils.ts line 584). When Reset is clicked, the sort order resets to Ascending instead of the expected Descending default. Staging-only regression, PR merged 2026-04-15. DeployBlockerCash label is correctly set - this is a Frontend bug in the App repo. Assigned: @bernhardoj (author), @aimane-chnaif, @JS00001, @luacmartins (approvers).

[trjExpensify]

Agree this is a bug. Minor though with a very easy workaround in the meantime, IMO.

Nevertheless @bernhardoj, one to fix ASAP. 👍