Skip to content

[Due for payment 2025-12-26] Reports - Search query contains columns: when opening recent search #77867

Closed

Description

@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.2.79-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #77673
Email or phone of affected tester (no customers): sodijsdoinjsosjoidjiso@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Search

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to Reports > Reports.
  3. Type anything in the search field and hit Enter.
  4. Click Columns.
  5. Make some changes to the selection > Save.
  6. Click Expenses tab.
  7. Click on the search field.
  8. Click on the recent search from Step 3.
  9. Click Expenses tab.
  10. Click on the search field.
  11. Click on the recent search from Step 3.

Expected Result:

Search query will not contain columns:

Actual Result:

Search query contains columns: when opening recent search.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @sonialiap

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 17, 2025
  2. melvin-bot commented on Dec 17, 2025

    @melvin-bot

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

  3. melvin-bot commented on Dec 17, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 17, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 17, 2025

    @github-actions
    Contributor

    👋 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.
  6. m-natarajan commented on Dec 17, 2025

    @m-natarajan

    MacOS Monterey / Chrome
    Web v9.2.81-0 PR:77837
    Not repro

    Screen.Recording.2025-12-17.at.21.42.06.mp4
  7. IuliiaHerets commented on Dec 18, 2025

    @IuliiaHerets

    Windows 11 / Chrome, v9.2.81-4
    Not reproduced

    search.query.mp4
  8. luacmartins commented on Dec 18, 2025

    @luacmartins
    Contributor

    Fixed

  9. linked a pull request that will close this issueFix custom columns blocker #2 #77888on Dec 19, 2025
  10. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 19, 2025
  11. changed the title [-]Reports - Search query contains columns: when opening recent search[/-] [+][Due for payment 2025-12-26] Reports - Search query contains columns: when opening recent search[/+] on Dec 19, 2025
  12. melvin-bot commented on Dec 19, 2025

    @melvin-bot

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

  13. melvin-bot commented on Dec 19, 2025

    @melvin-bot

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

    If no regressions arise, payment will be issued on 2025-12-26. 🎊

  14. melvin-bot commented on Dec 19, 2025

    @melvin-bot

    @luacmartins / @JS00001 @sonialiap 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]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions