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-06-11] [Simplified Actions] Incorrect system message for amount change after P2P expense becomes unreported #62722
Version Number: 9.1.51-0 Reproducible in staging?: Yes Reproducible in production?: Unable to check, new feature If this was caught during regression testing, add the test name, ID and link from TestRail:#58020 Email or phone of affected tester (no customers):applausetester+sjdoidwsn11j12@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Mac 15.4 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Submit two expenses to any user.
In 1:1 DM, click on the expense preview.
Click More > Delete.
Delete the report.
Go to self DM.
Click on any expenses from the deleted report.
Click Amount.
Edit the amount and save it.
Expected Result:
The system message for amount change will be "changed the amount to y (previously x)".
Actual Result:
The system message for amount change is "changed the amount to y (previously x)", then changes to "set the amount to y".
👋 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 [-][Simplified Actions] Incorrect system message for amount change after expense becomes unreported[/-][+][Simplified Actions] Incorrect system message for amount change after P2P expense becomes unreported[/+]on May 28, 2025
changed the title [-][Simplified Actions] Incorrect system message for amount change after P2P expense becomes unreported[/-][+][Due for payment 2025-06-11] [Simplified Actions] Incorrect system message for amount change after P2P expense becomes unreported[/+]on Jun 4, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.58-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@allgandalf@garrettmknight@allgandalf 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 May 24, 2025
Triggered auto assignment to @garrettmknight (
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 May 24, 2025
Triggered auto assignment to @pecanoro (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 24, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 24, 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:
twilight2294 commentedon May 24, 2025
BE bug
pecanoro commentedon May 26, 2025
@garrettmknight Are you able to reproduce? My message doesn't change so not sure if I am missing some step:
pecanoro commentedon May 26, 2025
Ok, I managed to reproduce, it only happens if the report was from 1:1 and not in a workspace
17 remaining items
[-][Simplified Actions] Incorrect system message for amount change after expense becomes unreported[/-][+][Simplified Actions] Incorrect system message for amount change after P2P expense becomes unreported[/+]melvin-bot commentedon Jun 3, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
[-][Simplified Actions] Incorrect system message for amount change after P2P expense becomes unreported[/-][+][Due for payment 2025-06-11] [Simplified Actions] Incorrect system message for amount change after P2P expense becomes unreported[/+]melvin-bot commentedon Jun 4, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jun 4, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.58-4 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-06-11. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jun 4, 2025
@allgandalf @garrettmknight @allgandalf 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]
allgandalf commentedon Jun 9, 2025
Lets close this one
luacmartins commentedon Jun 9, 2025
Closing!