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-08] Remove the rterRejectedExpense warning when a submitter edits the expense #70484
changed the title [-]Remove the rterRejectedExpense warning when a submitter edits the expense[/-][+][Due for payment 2025-12-08] Remove the rterRejectedExpense warning when a submitter edits the expense[/+]on Dec 1, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.66-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@mananjadhav / @truph01 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 12, 2025
Triggered auto assignment to @lschurr (
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.mananjadhav commentedon Sep 14, 2025
Will pick this tomorrow.
mananjadhav commentedon Sep 17, 2025
Will pick this once the current bugs are fixed.
melvin-bot commentedon Sep 22, 2025
@mananjadhav Eep! 4 days overdue now. Issues have feelings too...
23 remaining items
mananjadhav commentedon Nov 24, 2025
PR is raised, being reviewed
mananjadhav commentedon Nov 27, 2025
PR was merged today.
[-]Remove the rterRejectedExpense warning when a submitter edits the expense[/-][+][Due for payment 2025-12-08] Remove the rterRejectedExpense warning when a submitter edits the expense[/+]melvin-bot commentedon Dec 1, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 1, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.66-3 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-08. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Dec 1, 2025
@mananjadhav / @truph01 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 2, 2025
We can wait for few days and close this one. Payout for this will be handled with the project.
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 2 days.