[Due for payment 2025-05-14] [Due for payment 2025-05-08] Reports - Unable to search for task by simply typing "keyword" in the search query

[mitarachim]

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.1.33-3
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: #59672
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Search

Action Performed:

1. Go to staging.new.expensify.com
2. Create a new workspace.
3. Submit an expense with "any" as Description and "thing" as Merchant.
4. Create a task with "any" as Title and "thing" as Description.
5. Go to Reports.
6. Click on the search field.
7. Type - type:expense status:all any and hit Enter.
8. Type - type:expense status:all thing and hit Enter.
9. Note that the expense from Step 3 is returned with the search query from Step 7 and 8.
10. Go to Tasks.
11. Type - type:task status:all any and hit Enter.
12. Type - type:task status:all thing and hit Enter.

Expected Result:

• Search should be able to find the keyword in task title or description and return the relevant result.
• Search page should return "Nothing to show" empty state when there is no relevant result.

Actual Result:

• Search is not able to find the keyword in task title or description when the search query is done without title: and description:
• Instead of showing "Nothing to show" empty state, it shows the error page -
  Oops... Something went wrong
  Your request could not be completed. Please try again later.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6816075_1745909536816.20250429_144410.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @OfstadC

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @inimaga (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[luacmartins]

@JS00001

[inimaga]

New feature being introduced #59672. Removing DeployBlocker label

[luacmartins]

NAB we just need to make the filter global

[JS00001]

This PR was reverted and is now off of staging

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.38-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Revert "Add New Task Section to Reports" #61064

If no regressions arise, payment will be issued on 2025-05-08. 🎊

[melvin-bot]

@inimaga / @JS00001 @OfstadC @inimaga / @JS00001 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.40-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Revert "Add New Task Section to Reports" #61064

If no regressions arise, payment will be issued on 2025-05-14. 🎊

[melvin-bot]

@inimaga / @JS00001 @OfstadC @inimaga / @JS00001 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[JS00001]

Doesnt need payment, this was fixed internally