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 - System message for amount edit is shown when the amount is saved without edit #71012
Version Number: 9.2.15-1 PR:65001 Reproducible in staging?: N Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers):jsdoinjosdjosjniosdj@gmail.com Issue reported by: Applause - Internal Team
Action Performed:
Go to 65001.pr-testing.expensify.com
Go to workspace chat
Create an expense with negative amount
Open the transaction thread
Click Report
Click Remove from report
Go to self DM
Open the unreported expense
Click Amount
Without editing the amount, click Save
Expected Result:
There will be no system message for amount edit since the amount is saved without edit
Actual Result:
System message for amount edit is shown when the amount is saved without edit
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6952495_1758559874085.Screen_Recording_2025-09-23_at_00.49.09.mp4
👋 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 22, 2025
Triggered auto assignment to @alexpensify (
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 22, 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 22, 2025
Triggered auto assignment to @luacmartins (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Sep 22, 2025
💬 A slack conversation has been started in #expensify-open-source
luacmartins commentedon Sep 22, 2025
@lanitochka17 is this a deploy blocker? The test steps mention using
65001.pr-testing.expensify.comas the test base. That PR is not merged yet.luacmartins commentedon Sep 22, 2025
Not reproducible in staging, this flow doesn't exist there.
8 remaining items
luacmartins commentedon Oct 6, 2025
This is being worked on in the original PR
melvin-bot commentedon Oct 9, 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.
pasyukevich commentedon Oct 10, 2025
The original PR has been merged - the issue is not reproducible on stage
Screen.Recording.2025-10-10.at.17.40.47.mov
melvin-bot commentedon Oct 13, 2025
@pasyukevich Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Oct 13, 2025
@pasyukevich Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
luacmartins commentedon Oct 13, 2025
Closing since the issue is no longer reproducible and this was a regression.