[Due for payment 2025-09-02] [Due for payment 2025-08-29] [$250] Improve UX when `Filters` are selected but not visible.

[JmillsExpensify]

In order to improve the usability of UI filters on the Reports page, and specifically help users understand when a filter has been selected even if not visible, let's add a Filters (X) pattern to the Reports page.

The finer details for this update include:

• Filters (X) will only apply when filters are selected in Filters, for which an "exposed" filter does not exist.
• X equals the number of filters in Filters that are not an exposed filter
• For clarity, "exposed" filters appear immediately above the table, so: type, status, date, from (though we also have Feed and Posted date for certain default searches in the Accounting section)

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021955232355477239590
• Upwork Job ID: 1955232355477239590
• Last Price Increase: 2025-08-12

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @JmillsExpensify

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021955232355477239590

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @dukenv0307 (External)

[melvin-bot]

Current assignee @JmillsExpensify is eligible for the NewFeature assigner, not assigning anyone new.

[mkzie2]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Improve UX when Filters are selected but not visible

What is the root cause of that problem?

New feature

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

We can include the (X) after the filter text here. The X is the length of flatFilters array

text={`${translate('search.filtersHeader')}${flatFilters.length > 0 ? ` (${flatFilters.length})` : ''}`}

App/src/components/Search/SearchPageHeader/SearchFiltersBar.tsx

Line 567 in d1ecdb1

text={translate('search.filtersHeader')}

Or we can update search.filtersHeader translation with the new parameter and display the number if it's not 0.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

NA

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.