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-28] [$250] Expense - App allows to merge negative expense with IOU expense, negative amount is not saved #72143
Version Number: 9.2.28-0 Reproducible in staging?: Y Reproducible in production?: 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):sdijsnoisjnosij@gmail.com Issue reported by: Applause - Internal Team
Action Performed:
Go to staging.new.expensify.com
Go to 1:1 DM
Submit an expense to the user
Go to workspace chat
Create an expense with negative amount in workspace chat
Open the expense thread
Click More > Merge
Select the IOU expense from Step 3 > Continue
Select the negative amount for Amount section
Select the IOU report for Report section
Click Continue > Merge expenses
Expected Result:
App should not allow to merge negative expense with IOU expense because the negative amount cannot be preserved
Actual Result:
App allows to merge negative expense with IOU expense. Although the negative amount is selected, the amount of the merged expense is not negative
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 evidenceBug6969101_1759962567165.Screen_Recording_2025-10-09_at_06.25.32.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.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.35-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@Pujan92@dylanexpensify 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 Oct 8, 2025
Triggered auto assignment to @dylanexpensify (
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 @neil-marcellini (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.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:
melvin-bot commentedon Oct 8, 2025
💬 A slack conversation has been started in #expensify-open-source
lakchote commentedon Oct 9, 2025
cc @pasyukevich @Krishna2323 @ZhenjaHorbach @nkuoch @luacmartins
31 remaining items
melvin-bot commentedon Oct 21, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.35-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-10-28. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Oct 21, 2025
@Pujan92 @dylanexpensify 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]
melvin-bot commentedon Oct 22, 2025
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
dylanexpensify commentedon Oct 28, 2025
Payment summary:
Contributor+: @Pujan92 $250 via NewDot
Please apply/request!
melvin-bot commentedon Oct 28, 2025
Payment Summary
Upwork Job
BugZero Checklist (@dylanexpensify)
melvin-bot commentedon Oct 29, 2025
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
melvin-bot commentedon Oct 31, 2025
@dylanexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
JmillsExpensify commentedon Nov 3, 2025
$250 approved for @Pujan92
melvin-bot commentedon Dec 20, 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.