Repository navigation
[Due for payment 2025-11-13] [$250] Expense report with a negative total amount can't be manually marked as paid #72159
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.2.28-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #65001
Email or phone of affected tester (no customers): sdijsnoisjnosij@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Search
Action Performed:
- Go to staging.new.expensify.com
- Go to workspace chat.
- Create an expense with negative amount in workspace chat.
- Click Submit and Approve.
- Go to Reports > Pay.
Expected Result:
The expense report with a negative total amount shows the Pay button with the option to manually mark as paid, like Classic.
Actual Result:
The expense report with negative total amount doesn't show the Pay button.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Bug6969254_1759979945688.Screen_Recording_2025-10-09_at_11.14.06.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021976684117993762534
- Upwork Job ID: 1976684117993762534
- Last Price Increase: 2025-10-10
- Automatic offers:
- FitseTLT | Reviewer | 109144445
Activity
melvin-bot commentedon Oct 9, 2025
Triggered auto assignment to @carlosmiceli (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 9, 2025
Triggered auto assignment to @trjExpensify (
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 9, 2025
💬 A slack conversation has been started in #expensify-open-source
45 remaining items
melvin-bot commentedon Nov 6, 2025
@FitseTLT @trjExpensify 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]
trjExpensify commentedon Nov 13, 2025
👋 @FitseTLT checklist time, here!
mukhrr commentedon Nov 17, 2025
@FitseTLT kindly bump here #72159 (comment)
trjExpensify commentedon Nov 17, 2025
Still awaiting the checklist, Melv.
FitseTLT commentedon Nov 19, 2025
BugZero Checklist:
[Contributor] 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: More of a new feature
[Contributor] 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:
[Contributor] 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
Precondition:
Test:
Do we agree 👍 or 👎
FitseTLT commentedon Nov 19, 2025
Sorry for the delay
trjExpensify commentedon Nov 19, 2025
Thanks! Payment summary as follows:
trjExpensify commentedon Nov 19, 2025
nice, that was fast. Paid @mukhrr... closing!