[Payment due 2026-03-06] [$250] Reports - Current account does not appear in search result when searched with You or Me

[mitarachim]

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.25-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: #82490
Email or phone of affected tester (no customers): applausetester+abbbs40942@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.2 / Chrome
App Component: Search

Action Performed:

Precondition:

• Account has at least 12 contacts.

1. Go to staging.new.expensify.com
2. Go to Reports > Expenses.
3. Open From quick filter.
4. Type You or Me in the search field.

Expected Result:

Current account will show up at the top of the results.

Actual Result:

Current account does not appear in search result when searched with You or Me.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7086424_1771884486879.6.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022026062143608683965
• Upwork Job ID: 2026062143608683965
• Last Price Increase: 2026-02-23

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #82490

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[melvin-bot]

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

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