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-25] Expense - User is marked as selected on recipient list when expense amount is negative #77619
Version Number: 9.2.78-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#74964 Email or phone of affected tester (no customers):sjdoisjdosijodsnj@gmail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Mac 26.1 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Account has no workspace.
Go to staging.new.expensify.com
Open FAB > Create expense > Manual.
Enter amount > Next.
Select any user (not workspace chat).
On confirm page, click RHP back button twice.
Add negative sign to the amount > Next.
Click Next.
Click Create expense.
Expected Result:
In Step 6, after flipping the amount to negative, user should be hidden on recipient list because we cannot submit negative expense for p2p expense.
Actual Result:
In Step 6, after flipping the amount to negative, user is still selected on the recipient list.
In Step 8, after submitting negative expense to the user, the negative sign is not seen in the IOU report.
👋 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 - User is marked as selected on recipient list when expense amount is negative[/-][+][Due for payment 2025-12-25] Expense - User is marked as selected on recipient list when expense amount is negative[/+]on Dec 18, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.81-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@madmax330@strepanier03 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 Dec 13, 2025
Triggered auto assignment to @strepanier03 (
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 Dec 13, 2025
Triggered auto assignment to @madmax330 (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 13, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Dec 13, 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 Dec 15, 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.
dmkt9 commentedon Dec 15, 2025
This is from my PR #74964.
I have submitted a PR to resolve this regression: #77648
1 remaining item
melvin-bot commentedon Dec 15, 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.
melvin-bot commentedon Dec 15, 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.
madmax330 commentedon Dec 15, 2025
Should be covered in: #77648
m-natarajan commentedon Dec 15, 2025
Not repro, Windows 11 / Chrome, iPhone 15 , v9.2.78-2
Retest.5.MP4
neg.iou.mp4
amyevans commentedon Dec 15, 2025
All set ^
[-]Expense - User is marked as selected on recipient list when expense amount is negative[/-][+][Due for payment 2025-12-25] Expense - User is marked as selected on recipient list when expense amount is negative[/+]melvin-bot commentedon Dec 18, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 18, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.81-5 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-25. 🎊
melvin-bot commentedon Dec 18, 2025
@madmax330 @strepanier03 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]