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
Reports - Violation errors don't appear on the report page #66204
Version Number: v9.1.81-4 Reproducible in staging?: Yes Reproducible in production?: Unable to check on prod - onyx error If this was caught during regression testing, add the test name, ID and link from TestRail:#65239 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Device used: Windows 11 / Chrome App Component: Other
Action Performed:
Preconditions:
Create a workspace and invite an employee. As an employee, open WS chat and create some expenses
Already found the transactionID by Inspect Element > Network > OpenReport > search transaction on the Response
Open the Reports page/Search money request
Open the console
Run the script (replace transactionID that is already found on the precondition)
👋 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.
Update should show condition for some violations #65239: Directly changed useTransactionViolations filtering logic and added shouldShowViolation, likely hiding violations on the Reports page while still showing them in the expense view.
It's not a bug; to make it show on the Reports page with the mock data Onyx.update, the original transaction should have at least a violation, then the violation can be merged into the snapshot.
Activity
melvin-bot commentedon Jul 15, 2025
Triggered auto assignment to @bfitzexpensify (
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 Jul 15, 2025
Triggered auto assignment to @MonilBhavsar (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jul 15, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jul 15, 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:
rushatgabhane commentedon Jul 15, 2025
@BlameGPT please confirm the PR
BlameGPT commentedon Jul 15, 2025
Lowkey sus PRs fr fr
If not above, check these
nkdengineer commentedon Jul 15, 2025
It's not a bug; to make it show on the Reports page with the mock data
Onyx.update, the original transaction should have at least a violation, then the violation can be merged into the snapshot.nkdengineer commentedon Jul 15, 2025
@nlemma Sorry, I missed a precondition in the test step
MonilBhavsar commentedon Jul 16, 2025
Thanks for clarifying! @nlemma can we please get a retest. Thanks!
nlemma commentedon Jul 16, 2025
Just retested and PR is a pass 🚀
MonilBhavsar commentedon Jul 16, 2025
Thank you for checking!