[Due for payment 2026-08-19] Violations by submitter row is highlighted when Submitted violation filter is not selected

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.52-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: #97067
Email or phone of affected tester (no customers): applausetester+ssndjois2jd1@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Search

Action Performed:

Precondition:

• Enable Rules.
• Invite user B to the workspace.
• User B submits an expense without category in the invited workspace.
• Perform the steps below as owner:

1. Go to staging.new.expensify.com
2. Go to Spend > Violations by submitter.
3. Click Has filter.
4. Deselect Submitted violation.
5. Select any other filter except Submitted violation.
6. Click Apply.

Expected Result:

Violations by submitter row will no longer be highlighted when Submitted violation filter is not selected.

Actual Result:

Violations by submitter row is still highlighted when Submitted violation filter is not selected.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7230591_1786405901034.19.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7230591

Issue Owner

Current Issue Owner: @cretadn22

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/011e7254baaedd185c138ac80f43805350c267531faa7fe2955f69df4440511d

https://platform.applause.com/services/links/v1/external/b62d213cc4a93327e3735aced17cbb12f5141d9e733e95744740c4e823384ab6

[melvin-bot]

@neil-marcellini recently merged #97067, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

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

[melvin-bot]

@neil-marcellini @cretadn22 you have been assigned to this deploy blocker because you reviewed the offending PR: #97067

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