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
Expense - Rejected expense is not displayed as rejected on member´s side. #70596
Version Number: 9.2.14-2 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 TestRail:#62787 Email or phone of affected tester (no customers):ibellicotest+1786@gmail.com Issue reported by: Applause Internal Team Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 11 / Chrome App Component: Money Requests
Action Performed:
Prerequisite: Have two accounts opened on two different devices or environments.
Prerequisite 2: User A has at least one workspace with delayed submissions and approvals enabled.
Open the Expensify app.
Open any workspace chat.
Tap on header and select "Members"
Invite User B as member of the workspace chat.
Return to chat.
Create a manual expense.
As User A, open the expense report.
Tap on "More" and select "Reject"
Enter any reason, and reject the expense.
Note that a "This expense was rejected" message can be seen on top of report.
Return to chat.
Note that a "Review Required" message can be seen on expense preview.
As User B, open the workspace chat.
Note that no "Review required" message is seen on expense preview.
Open the expense.
Note that no "This expense was rejected" message can be seen on top of report.
Expected Result:
When an expense is rejected by the admin of a workspace, the expense should be displayed as "Rejected" on member´s side also.
Actual Result:
When an expense is rejected by the admin of a workspace, no "Review Required" message can be seen on preview on member´s side, and also, no "This expense was rejected" message can be seen inside the report.
👋 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.
Activity
melvin-bot commentedon Sep 15, 2025
Triggered auto assignment to @clarajones-expensify (
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 @techievivek (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.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:
melvin-bot commentedon Sep 15, 2025
💬 A slack conversation has been started in #expensify-open-source
lakchote commentedon Sep 16, 2025
Should be behind a beta see #70579 (comment)
garrettmknight commentedon Sep 16, 2025
I'm actually not sure this is a bug. I think this might be expected behavior since this is a warn and not an outright violation.
IuliiaHerets commentedon Sep 16, 2025
The feature is not available with Gmail address.
IuliiaHerets commentedon Sep 16, 2025
But issue is still repro with Expensify account, Win11, Chrome, Build: 9.2.14-4
web.chrome.3.mp4
mananjadhav commentedon Sep 16, 2025
@garrettmknight Can we confirm if this is a bug?
garrettmknight commentedon Sep 17, 2025
This is the expected behavior for a warn as mentioned here. I tihnk we can close.