You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-11-26] [$250] Reports - Action field shows "search.filters.action.sjdsdno" when searched with action:sjdsdno #72961
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:
Go to staging.new.expensify.com
Go to Reports > Expenses.
Type action:sjdsdno and tap Enter.
Open Filters.
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
👋 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:
Identify the pull request that introduced this issue and revert it.
[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:
Go to staging.new.expensify.com
Go to Reports > Expenses.
Type "action:invalid" and tap Enter.
Open Filters.
Scroll down to Action field.
Note that action field should be empty, since the query is invalid.
Activity
melvin-bot commentedon Oct 20, 2025
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.melvin-bot commentedon Oct 20, 2025
Triggered auto assignment to @arosiclair (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 20, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 20, 2025
👋 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:
78 remaining items
melvin-bot commentedon Nov 26, 2025
Current assignee @eh2077 is eligible for the External assigner, not assigning anyone new.
mallenexpensify commentedon Nov 26, 2025
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.
dmkt9 commentedon Nov 26, 2025
@mallenexpensify Thank you. The payment request has been submitted.
melvin-bot commentedon Nov 26, 2025
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
mallenexpensify commentedon Nov 26, 2025
@dmkt9 paid, summary updated above.
@eh2077 plz complete the BZ checklist.
eh2077 commentedon Nov 27, 2025
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:
Test:
Do we agree 👍 or 👎
eh2077 commentedon Nov 27, 2025
@mallenexpensify Checklist done, thanks!
melvin-bot commentedon Dec 1, 2025
@luacmartins, @mallenexpensify, @eh2077, @dmkt9 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
mallenexpensify commentedon Dec 2, 2025
Test case created
Thx!!
garrettmknight commentedon Dec 18, 2025
$250 approved for @eh2077