Skip to content

[Due for payment 2025-11-26] [$250] Reports - Action field shows "search.filters.action.sjdsdno" when searched with action:sjdsdno #72961

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.34-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #71800
Email or phone of affected tester (no customers): jsodinjsoidjoijsos@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Search

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to Reports > Expenses.
  3. Type action:sjdsdno and tap Enter.
  4. Open Filters.
  5. Scroll down to Action field.

Expected Result:

Action field should be empty, since the query is invalid.

Actual Result:

Action field shows "search.filters.action.sjdsdno" when searched with action:sjdsdno

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021980376594677378504
  • Upwork Job ID: 1980376594677378504
  • Last Price Increase: 2025-11-26
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @

Activity

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

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (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 Oct 20, 2025

    @melvin-bot

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

  4. melvin-bot commented on Oct 20, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 20, 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. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Oct 20, 2025
  7. 78 remaining items

  8. melvin-bot commented on Nov 26, 2025

    @melvin-bot

    Current assignee @eh2077 is eligible for the External assigner, not assigning anyone new.

  9. mallenexpensify commented on Nov 26, 2025

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @dmkt9 paid $250 via Upwork
    Contributor+: @eh2077 due $250 via NewDot

    @dmkt9 can you please accept the job below? Please reply here and tag me once you have.
    https://www.upwork.com/jobs/~021993471689230055358

    @eh2077 plz complete the BZ checklist.

  10. dmkt9 commented on Nov 26, 2025

    @dmkt9
    Contributor

    @mallenexpensify Thank you. The payment request has been submitted.

  11. melvin-bot commented on Nov 26, 2025

    @melvin-bot

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

  12. mallenexpensify commented on Nov 26, 2025

    @mallenexpensify
    Contributor

    @dmkt9 paid, summary updated above.
    @eh2077 plz complete the BZ checklist.

  13. eh2077 commented on Nov 27, 2025

    @eh2077
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: https://github.com/Expensify/App/pull/63753/files#r2567638992

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: NA

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Precondition:

    • NA

    Test:

    1. Go to staging.new.expensify.com
    2. Go to Reports > Expenses.
    3. Type "action:invalid" and tap Enter.
    4. Open Filters.
    5. Scroll down to Action field.
    6. Note that action field should be empty, since the query is invalid.

    Do we agree 👍 or 👎

  14. eh2077 commented on Nov 27, 2025

    @eh2077
    Contributor

    @mallenexpensify Checklist done, thanks!

  15. melvin-bot commented on Dec 1, 2025

    @melvin-bot

    @luacmartins, @mallenexpensify, @eh2077, @dmkt9 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  16. mallenexpensify commented on Dec 2, 2025

    @mallenexpensify
    Contributor
  17. garrettmknight commented on Dec 18, 2025

    @garrettmknight
    Contributor

    $250 approved for @eh2077

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions