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-10-31] Expense - Old amount in the system message does not show negative sign #72137
Version Number: 9.2.28-0 Reproducible in staging?: Y 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:#65001 Email or phone of affected tester (no customers):djojsijiosjsdi@gmail.com Issue reported by: Applase - Internal Team
Action Performed:
Go to staging.new.expensify.com
Go to self DM
Create an expense with negative amount
Open transaction thread
Go offline
Click Amount
Edit the amount and save it
Expected Result:
The old amount in the system message will show negative sign
Actual Result:
The old amount in the system message does not show negative sign
It shows negative sign after going online
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 evidenceBug6969080_1759961517363.Screen_Recording_2025-10-09_at_05.37.17.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.
changed the title [-]Expense - Old amount in the system message does not show negative sign[/-][+][Due for payment 2025-10-31] Expense - Old amount in the system message does not show negative sign[/+]on Oct 24, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.37-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@akinwale@JmillsExpensify 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]
[@akinwale] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: N/A
[@akinwale] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[@akinwale] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Launch Expensify.
Go to self DM.
Create an expense with a negative amount.
Open the transaction thread.
Go offline.
Click Amount.
Edit the amount and save it.
Verify that the system message shows the old amount prefixed with the negative sign.
Activity
melvin-bot commentedon Oct 8, 2025
Triggered auto assignment to @JmillsExpensify (
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 Oct 8, 2025
Triggered auto assignment to @mjasikowski (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 8, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 8, 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:
lakchote commentedon Oct 9, 2025
cc @pasyukevich @Krishna2323 @ZhenjaHorbach @nkuoch @luacmartins
19 remaining items
[-]Expense - Old amount in the system message does not show negative sign[/-][+][Due for payment 2025-10-31] Expense - Old amount in the system message does not show negative sign[/+]melvin-bot commentedon Oct 24, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Oct 24, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.37-8 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-10-31. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Oct 24, 2025
@akinwale @JmillsExpensify 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]
akinwale commentedon Oct 29, 2025
BugZero Checklist:
[@akinwale] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: N/A
[@akinwale] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[@akinwale] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Do we agree 👍 or 👎?
melvin-bot commentedon Oct 31, 2025
Payment Summary
Upwork Job
BugZero Checklist (@JmillsExpensify)
JmillsExpensify commentedon Nov 4, 2025
Payment summary above is correct.
JmillsExpensify commentedon Nov 4, 2025
All done here
garrettmknight commentedon Nov 4, 2025
$250 approved for @akinwale