[$250] Search - Workspace switcher resets to Expensify after manually searching via search input

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.53-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to Search
3. Click Filters
4. Apply any filter and click Save
5. Click View results
6. Open workspace switcher and select a workspace
7. Click on the search input field
8. Type any query and hit Enter

Expected Result:

The workspace switcher will not change after manually typing on the search field and hitting Enter

Actual Result:

The workspace switcher changes to Expensify after manually typing on the search field and hitting Enter

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6644138_1729758750803.20241024_162621.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021851453987704756817
• Upwork Job ID: 1851453987704756817
• Last Price Increase: 2024-11-06
• Automatic offers:
• Krishna2323 | Contributor | 104839473

Issue Owner

Current Issue Owner: @eVoloshchak

[melvin-bot]

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

[lanitochka17]

@RachCHopkins FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[lanitochka17]

We think that this bug might be related to #wave-control

[Krishna2323]

Edited by proposal-police: This proposal was edited at 2024-10-24 14:37:30 UTC.

Proposal


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

Search - Workspace switcher resets to Expensify after manually searching via search input

What is the root cause of that problem?

• The policyID isn't included in the input.
• The policyID is not set when we are passing the standardizedQuery to buildSearchQueryString.
  

  App/src/components/Search/SearchPageHeader.tsx

  Lines 338 to 351 in 81e877a

  	const onSubmit = () => {
  	if (!inputValue) {
  	return;
  	}
  	const inputQueryJSON = SearchQueryUtils.buildSearchQueryJSON(inputValue);
  	if (inputQueryJSON) {
  	const standardizedQuery = SearchQueryUtils.standardizeQueryJSON(inputQueryJSON, cardList, taxRates);
  	const query = SearchQueryUtils.buildSearchQueryString(standardizedQuery);
  	SearchActions.clearAllFilters();
  	Navigation.navigate(ROUTES.SEARCH_CENTRAL_PANE.getRoute({query}));
  	} else {
  	Log.alert(`${CONST.ERROR.ENSURE_BUGBOT} user query failed to parse`, inputValue, false);
  	}
  	};

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


• We can the value of activeWorkspaceID and if it is available, we can set the policyID. Or instead of activeWorkspaceID, we can check for queryJSON.policyID

    const onSubmit = () => {
        if (!inputValue) {
            return;
        }
        const inputQueryJSON = SearchQueryUtils.buildSearchQueryJSON(inputValue);
        if (inputQueryJSON) {
            const standardizedQuery = SearchQueryUtils.standardizeQueryJSON(inputQueryJSON, cardList, taxRates);
            if (activeWorkspaceID) {
                standardizedQuery.policyID = activeWorkspaceID;
            }
            const query = SearchQueryUtils.buildSearchQueryString(standardizedQuery);
            SearchActions.clearAllFilters();
            Navigation.navigate(ROUTES.SEARCH_CENTRAL_PANE.getRoute({query}));
        } else {
            Log.alert(`${CONST.ERROR.ENSURE_BUGBOT} user query failed to parse`, inputValue, false);
        }
    };

• We should also look for the same bug in other places.

What alternative solutions did you explore? (Optional)

Result

[shahinyan11]

Edited by proposal-police: This proposal was edited at 2024-10-24 14:57:34 UTC.

Proposal

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

Search - Workspace switcher resets to Expensify after manually searching via search input

What is the root cause of that problem?

Here we build search query from inputValue which does not contain policyId

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

I don't know if there might be other parameters in the URL that might also be missed like policyId, so I'm providing a solution below to not miss any parameter.

Update inputQueryJSON parameter to {...queryJSON, ...inputQueryJSON}.

What alternative solutions did you explore? (Optional)

[RachCHopkins]

Will triage tomorrow.

[RachCHopkins]

Easy to Repro. I did not know the workspace switcher was a thing!

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

@eVoloshchak, @RachCHopkins Eep! 4 days overdue now. Issues have feelings too...

[RachCHopkins]

@eVoloshchak how do you feel about the proposals so far?

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[eVoloshchak]

@Krishna2323's proposal looks good to me!

We should also look for the same bug in other places.

The same bug occurs with a simple search (without selecting a category), this does seem to resolve this issue for any search query

🎀👀🎀 C+ reviewed!

[melvin-bot]

Triggered auto assignment to @lakchote, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[lakchote]

@Krishna2323's proposal LGTM.

[melvin-bot]

📣 @Krishna2323 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

[Krishna2323]

PR will be up today.

[Krishna2323]

@lakchote @eVoloshchak, I’m unsure what to do with the search router. Currently, it removes the active workspace when we search. Should we update it to maintain the workspace selection during a search, or is it expected behavior to remove the selection to show all results?

Monosnap.screencast.2024-11-13.04-07-07.mp4

[lakchote]

@Krishna2323 in your test you switch to another workspace, then you search for something and select a result corresponding to yet another workspace.

In my opinion, we should switch to the workspace of the search's result selected in the search router.

What's your opinion @luacmartins?

[luacmartins]

I think this issue is similar to #49637, where we want to keep the workspace switcher and not clear it when the user makes a search either typed in the router or via the UI filters. cc @Kicu

[Kicu]

I agree, in fact this feels like a regression. I swear that I seem to remember working on this, and the scenario shown in the video from @Krishna2323 used to work 🤔

I believe when submitting the search query that the user typed in, we should check if there is a workspace selected, and if yes then add policyID to final query.
The mechanism that correctly sets workspace switcher when policyID is part of search query, is already in the code and works (I verified on stage).