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
Reject violation is shown on Reports > Expenses for rejected and unreported expense #70587
Version Number: 9.2.14-1 Reproducible in staging?: Y 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 TestRail:#62787 Email or phone of affected tester (no customers):sjdiojsdoinsjo@gmail.com Issue reported by: Applause - Internal Team
Action Performed:
Precondition:
Delayed submissions are disabled in Workflows settings
Go to staging.new.expensify.com
Go to workspace chat
Create an expense in workspace chat
Open expense report
Click More > Reject
Enter reason and click Reject expense
Go to self DM
→ "This expense was rejected" violation is not shown on the expense preview in self DM
Go to Reports > Expenses
Expected Result:
"This expense was rejected" violation will not be shown on the expense row on Reports > Expenses when the expense is rejected and unreported
Actual Result:
"This expense was rejected" violation is shown on the expense row on Reports > Expenses when the expense is rejected and unreported
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6945181_1757951482363.Screen_Recording_2025-09-15_at_23.47.26.mp4
👋 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.
@garrettmknight this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
The violation is removed when the expenses is moved to selfDM/unreported
Since it takes manual action to move it onto a report, and we're implementing logic to remove the violation when the expense is edited, I think that's just fine.
Activity
melvin-bot commentedon Sep 15, 2025
Triggered auto assignment to @stephanieelliott (
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 Sep 15, 2025
Triggered auto assignment to @Gonals (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Sep 15, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Sep 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:
13 remaining items
garrettmknight commentedon Sep 22, 2025
Same as above.
melvin-bot commentedon Sep 25, 2025
@garrettmknight Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
garrettmknight commentedon Sep 26, 2025
Same as above.
garrettmknight commentedon Sep 29, 2025
Same
melvin-bot commentedon Sep 29, 2025
@garrettmknight this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
garrettmknight commentedon Oct 2, 2025
Ok, finally took a minute to test: