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
[Due for payment 2025-11-11] [Reject] Expense - Rejected expense is not seen in a new report when rejected offline #70569
Version Number: 9.2.14-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 TestRail:#62787 Email or phone of affected tester (no customers):sdjiodsnjdosijdis@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Submit two expenses to worksace chat.
Open expense report.
Click Submit.
Go offline.
Open one of the expenses.
Click More > Reject.
Enter reason and save it.
Go back to main workspace chat.
Expected Result:
The rejected expense will be created in a new draft report.
Actual Result:
The rejected expense is not seen in a new report when rejected offline.
👋 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.
changed the title [-][Reject] Expense - Rejected expense is not seen in a new report when rejected offline[/-][+][Due for payment 2025-11-11] [Reject] Expense - Rejected expense is not seen in a new report when rejected offline[/+]on Nov 4, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.43-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@mananjadhav / @truph01@garrettmknight The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Sep 15, 2025
Triggered auto assignment to @trjExpensify (
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.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
Triggered auto assignment to @rlinoz (
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
rlinoz commentedon Sep 15, 2025
https://expensify.slack.com/archives/C01GTK53T8Q/p1757943373718019
trjExpensify commentedon Sep 15, 2025
@garrettmknight seems like he has a handle on this, might be better if you take over BZ?
48 remaining items
[-][Reject] Expense - Rejected expense is not seen in a new report when rejected offline[/-][+][Due for payment 2025-11-11] [Reject] Expense - Rejected expense is not seen in a new report when rejected offline[/+]melvin-bot commentedon Nov 4, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Nov 4, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.43-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-11-11. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Nov 4, 2025
@mananjadhav / @truph01 @garrettmknight The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
garrettmknight commentedon Nov 11, 2025
Will pay out as part of the project. QAs already exist here.
melvin-bot commentedon Nov 14, 2025
@garrettmknight Whoops! This issue is 2 days overdue. Let's get this updated quick!
mananjadhav commentedon Nov 16, 2025
This one can be closed now.