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
Expenses with fixed violations are listed under violation filter #107576
Version Number: 9.5.49-1 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:#107141 Email or phone of affected tester (no customers):gocemate+bazzo@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: windows 11/chrome App Component: Other
Action Performed:
Create workspace and enable Rules option
Go to workspace chat and create expenses with violation ( Duplicate potential)
Go to Spend> Display> Group by> Violation
Verify expenses with violation are displayed
Reset this filter
Edit one of duplicate expenses (change amount, merchant..), so the violation is fixed
Go to Spend> Display> Group by> Violation
Expected Result:
There should be no expenses displayed
Actual Result:
Fixed violation expenses are still displayed under violation filter
👋 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.
No regression confirmed.Add group-by:violation introduced this flow, but the evidence does not yet justify reverting it.
Violation grouping intentionally uses violations recorded when expenses were submitted or approved, rather than their current warnings. Resolving a duplicate afterward may therefore leave it in these results.
These establish intended semantics—not whether the reported expenses correctly qualify.
Missing evidence: The reproduction steps omit submission/approval history. No browser reproduction or affected search response was verified, so stale or incorrect membership remains possible.
Recommendation: Keep the blocker pending verification of that history and a fresh search response. If matching historical duplicate violations exist, persistence is expected; if they do not, investigate incorrect membership. Do not revert the feature solely on the current evidence.
Confidence: High on intended behavior; unresolved on this specific reproduction.
Activity
applause-bot commentedon Nov 20, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/59b2838fee059e6fc8f5bd056eb5ae4d039fbee9c04786e0a96f982d40befc0c
expensify-chore-bot commentedon Nov 20, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #107141
expensify-chore-bot commentedon Nov 20, 2026
@neil-marcellini you have been assigned to this deploy blocker because you reviewed the offending PR: #107141
expensify-chore-bot commentedon Nov 20, 2026
@nkdengineer you have been assigned to this deploy blocker because you authored the offending PR: #107141
expensify-chore-bot commentedon Nov 20, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 20, 2026
👋 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:
MelvinBot commentedon Nov 20, 2026
Investigation result
No regression confirmed. Add group-by:violation introduced this flow, but the evidence does not yet justify reverting it.
Violation grouping intentionally uses violations recorded when expenses were submitted or approved, rather than their current warnings. Resolving a duplicate afterward may therefore leave it in these results.
Supporting evidence
These establish intended semantics—not whether the reported expenses correctly qualify.
Missing evidence: The reproduction steps omit submission/approval history. No browser reproduction or affected search response was verified, so stale or incorrect membership remains possible.
Recommendation: Keep the blocker pending verification of that history and a fresh search response. If matching historical duplicate violations exist, persistence is expected; if they do not, investigate incorrect membership. Do not revert the feature solely on the current evidence.
Confidence: High on intended behavior; unresolved on this specific reproduction.
view run
nkdengineer commentedon Nov 20, 2026
@neil-marcellini I think it's not a bug as the group capture the violation at the submitted/approved time.
trjExpensify commentedon Nov 20, 2026
I agree, this is not a bug.