[RCA #75026] Task - "Assign to me" section is missing

[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.42-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #75026
Email or phone of affected tester (no customers): skdpmoskpskspskd@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Other

Action Performed:

1 .Go to staging.new.expensify.com
2. Open any chat.
3. Click + > Assign task.
4. Enter title > Next.
5. On confirm page, click Assignee.

Expected Result:

"Assign to me" section will show own account.

Actual Result:

"Assign to me" section is missing.

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: #75026

[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: #75026 - "use useSearchSelector hook and remove unused and duplicated code" by @mkzie2 (High confidence)
Related Issues: None

Recommendation: REVERT

PR #75026 introduced a parameter override bug in useSearchSelector.base.ts that prevents the current user option from appearing in task assignee selection. The fix would require careful refactoring of parameter precedence logic, which carries risk. Reverting is the safest path to unblock the deploy.

Labels: This is a frontend bug where the fix needs to happen in the App repository. The issue is only reproducible on staging (not production), which confirms it was introduced by a PR in the current deploy. Since PR #75026 caused the issue and the fix needs to happen in App, the DeployBlockerCash label should be KEPT and is correctly applied.

📋 Detailed Analysis

Evidence

PR #75026 refactored the useSearchSelector hook and modified how options are retrieved. The bug appears specifically in task assignee selection where the "Assign to me" section is missing.

Verification

Affected file: src/pages/tasks/TaskAssigneeSelectorModal.tsx

• Lines 101-107 display the "Assign to me" section based on optionsWithoutCurrentUser.currentUserOption
• This component calls useSearchSelector with getValidOptionsConfig: { includeCurrentUser: true } (line 56-58)

Bug location: src/hooks/useSearchSelector.base.ts

• Line 260-280: The SEARCH_CONTEXT_GENERAL case calls getValidOptions
• Line 261: Spreads ...getValidOptionsConfig (which contains includeCurrentUser: true)
• Line 272: Directly passes includeCurrentUser parameter - this was added in PR use useSearchSelector hook and remove unused and duplicated code #75026

Root Cause

The PR added a direct includeCurrentUser parameter at line 272 of useSearchSelector.base.ts. This parameter overrides the includeCurrentUser value from getValidOptionsConfig that was spread earlier.

In JavaScript object spreading, later properties override earlier ones:

{
  ...getValidOptionsConfig,  // includes includeCurrentUser: true
  includeCurrentUser,        // overrides with default value: false
}

Since TaskAssigneeSelectorModal only sets includeCurrentUser via getValidOptionsConfig and not as a direct hook parameter, it gets the default value of false (defined at line 166 of useSearchSelector.base.ts), causing currentUserOption to not be included in the results.

This prevents the "Assign to me" section from rendering in the task assignee selector modal.