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-12-10] [Reject] Expense - GBR remains in LHN after rejecting expense offline #70565
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):oijnoijoijjijnioj3@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
[User A] Submit an expense to User B.
[User B] Open IOU expense report.
[User B] Go offline.
[User B] Click More > Reject.
[User B] Enter reason and click Reject expense.
Expected Result:
GBR will disappear from LHN after rejecting expense offline.
Actual Result:
GBR remains in LHN after rejecting expense 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 - GBR remains in LHN after rejecting expense offline[/-][+][Due for payment 2025-12-10] [Reject] Expense - GBR remains in LHN after rejecting expense offline[/+]on Dec 3, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.70-0 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 @zanyrenney (
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 @grgia (
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:
53 remaining items
lakchote commentedon Nov 28, 2025
^ cc @truph01
mananjadhav commentedon Dec 2, 2025
PR was deployed on staging.
[-][Reject] Expense - GBR remains in LHN after rejecting expense offline[/-][+][Due for payment 2025-12-10] [Reject] Expense - GBR remains in LHN after rejecting expense offline[/+]melvin-bot commentedon Dec 3, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 3, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.70-0 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-12-10. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Dec 3, 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]
mananjadhav commentedon Dec 5, 2025
This is deployed to production and will be paid as a part of the project. Best to close this one in a few days.
mananjadhav commentedon Dec 8, 2025
I think it's safe to close this one out.
trjExpensify commentedon Dec 9, 2025
Do it!