[Due for payment 2026-01-05] [$250] Reports - Suggestion list visibility is inconsistent between in: and group-by:

[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.63-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: #74940
Email or phone of affected tester (no customers): dreamnitethedragon+yydyd373@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to https://staging.new.expensify.com/home
2. Login with new gmail account
3. Tap Reports
4. Enter group-by:
5. Select an option from suggestion list
6. Note after selecting "suggestion list" is not shown
7. Enter in:
8. Select an option from suggestion list
9. Note suggestion list is shown with selected item

Expected Result:

Suggestion list behavior for in: must be consistent with group-by:.

Actual Result:

For group-by:, the suggestion list not shown after selecting an option
But for in:, the suggestion list is shown even after selecting an option

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

Add any screenshot/video evidence

Bug7013154_1764081999707.Screenrecorder-2025-11-25-20-04-42-374.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021995858028033059491
• Upwork Job ID: 1995858028033059491
• Last Price Increase: 2025-12-09

Issue Owner

Current Issue Owner: @CortneyOfstad

[melvin-bot]

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

[abbasifaizan70]

Proposal

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

The suggestion list behavior is inconsistent between group-by: and in: filters in the search autocomplete. After selecting an option:

• For group-by:: The suggestion list correctly closes after selection (expected)
• For in:: The suggestion list remains visible after selection (inconsistent)

What is the root cause of that problem?

In SearchAutocompleteList.tsx, the IN filter case (lines 432-454) doesn't filter suggestions using alreadyAutocompletedKeys, unlike GROUP_BY which does. When a value is selected:

• GROUP_BY filters out already selected values and returns empty array when autocomplete value is empty, hiding the list
• IN always returns suggestions without filtering, keeping the list visible

The alreadyAutocompletedKeys Set tracks selected values but IN case ignores it.

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

Update the IN filter case to match GROUP_BY behavior by filtering out already selected reports and returning empty array when autocomplete value is empty after selection.

File: App/src/components/Search/SearchAutocompleteList.tsx (lines 432-454)

Add these lines at the beginning of the CONST.SEARCH.SYNTAX_FILTER_KEYS.IN case:

// If autocompleteValue is empty or just whitespace and we have already completed keys,
// return empty array to hide suggestion list (consistent with group-by behavior)
if (!autocompleteValue.trim() && alreadyAutocompletedKeys.size > 0) {
    return [];
}

Add .filter() to the recentReports line:

}).recentReports.filter((chat) => !alreadyAutocompletedKeys.has((chat.text ?? '').toLowerCase()));

This makes in: behavior consistent with group-by: by hiding the suggestion list after selection.

What alternative solutions did you explore? (Optional)

N/A

Demo

Screen.Recording.2025-11-26.at.3.23.10.AM.mov

[daledah]

Proposal

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

For group-by:, the suggestion list not shown after selecting an option
But for in:, the suggestion list is shown even after selecting an option

What is the root cause of that problem?

We don't have filter logic in case CONST.SEARCH.SYNTAX_FILTER_KEYS.IN like we did with CONST.SEARCH.SYNTAX_ROOT_KEYS.GROUP_BY

App/src/components/Search/SearchAutocompleteList.tsx

Lines 449 to 454 in 29e1abf

	return filteredReports.map((chat) => ({
	filterKey: CONST.SEARCH.SEARCH_USER_FRIENDLY_KEYS.IN,
	text: chat.text ?? '',
	autocompleteID: chat.reportID,
	mapKey: CONST.SEARCH.SYNTAX_FILTER_KEYS.IN,
	}));

App/src/components/Search/SearchAutocompleteList.tsx

Lines 463 to 468 in 29e1abf

	case CONST.SEARCH.SYNTAX_ROOT_KEYS.GROUP_BY: {
	const filteredGroupBy = groupByAutocompleteList.filter(
	(groupByValue) => groupByValue.toLowerCase().includes(autocompleteValue.toLowerCase()) && !alreadyAutocompletedKeys.has(groupByValue.toLowerCase()),
	);
	return filteredGroupBy.map((groupByValue) => ({filterKey: CONST.SEARCH.SEARCH_USER_FRIENDLY_KEYS.GROUP_BY, text: groupByValue}));
	}

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

We should add the filter logic to the case CONST.SEARCH.SYNTAX_FILTER_KEYS.IN to make it consistent with CONST.SEARCH.SYNTAX_ROOT_KEYS.GROUP_BY

                return filteredReports.map((chat) => ({
                    filterKey: CONST.SEARCH.SEARCH_USER_FRIENDLY_KEYS.IN,
                    text: chat.text ?? '',
                    autocompleteID: chat.reportID,
                    mapKey: CONST.SEARCH.SYNTAX_FILTER_KEYS.IN,
                })).filter((inValue) => inValue.text.toLowerCase().includes(autocompleteValue.toLowerCase()) && !alreadyAutocompletedKeys.has(inValue.text.toLowerCase()));

App/src/components/Search/SearchAutocompleteList.tsx

Lines 449 to 454 in 29e1abf

	return filteredReports.map((chat) => ({
	filterKey: CONST.SEARCH.SEARCH_USER_FRIENDLY_KEYS.IN,
	text: chat.text ?? '',
	autocompleteID: chat.reportID,
	mapKey: CONST.SEARCH.SYNTAX_FILTER_KEYS.IN,
	}));

Note: We should do the same with other filter keys.

What alternative solutions did you explore? (Optional)

Or we can remove logic filter in CONST.SEARCH.SYNTAX_ROOT_KEYS.GROUP_BY

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.

[melvin-bot]

@CortneyOfstad Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@CortneyOfstad Eep! 4 days overdue now. Issues have feelings too...

[melvin-bot]

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

[melvin-bot]

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