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-17] [$250] Cannot make an expense negative #53441
Version Number: 9.0.70-1 Reproducible in staging?: Y Reproducible in production?: Y If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@twisterdotcom Slack conversation (hyperlinked to channel name): ts_external_expensify_bugs
Action Performed:
SmartScan a receipt
Open the expense
Open the amount
Try to correct it to be negative. No way to add brackets or - sign.
Expected Result:
User able to enter minus, plus or Brackets
Actual Result:
User unable to enter minus, plus or Brackets
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
@ZhenjaHorbach 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:
@ZhenjaHorbach 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:
@ZhenjaHorbach 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.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
@pasyukevich does not require payment (Contractor) @waterim does not require payment (Contractor) @pac-guerreiro requires payment $250 in Upwork for review. @ZhenjaHorbach pending in NewDot for C+ review
📣 @pac-guerreiro! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
There was regression which was not handled by original C+ @ZhenjaHorbach. They were aware of that regression and didn't try to fix by themselves.
This issue was demoted and was open for external contributors(#72140 (comment))
And if this were a critical issue, the internal engineer could always assign the original developers
@pasyukevich does not require payment (Contractor) @waterim does not require payment (Contractor) @pac-guerreiro does not require payment (Contractor) @ZhenjaHorbach pending in NewDot for C+ review
Activity
melvin-bot commentedon Dec 4, 2024
Triggered auto assignment to @johncschuster (
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.[-]Cannot make an expense negative[/-][+][$250] Cannot make an expense negative[/+]melvin-bot commentedon Dec 9, 2024
Job added to Upwork: https://www.upwork.com/jobs/~021866173019746429432
melvin-bot commentedon Dec 9, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ZhenjaHorbach (
External)327 remaining items
isabelastisser commentedon Oct 20, 2025
BugZero Checklist:
@ZhenjaHorbach 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:
@ZhenjaHorbach 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:
@ZhenjaHorbach 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.
Regression Test Proposal Template
[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 👎
ZhenjaHorbach commentedon Oct 20, 2025
Oh
It was a long issue
I already forgot that I started it on Upwork
And now I'm getting a payment on ND 😅
isabelastisser commentedon Oct 20, 2025
Payment summary:
@pasyukevich does not require payment (Contractor)
@waterim does not require payment (Contractor)
@pac-guerreiro requires payment $250 in Upwork for review.
@ZhenjaHorbach pending in NewDot for C+ review
isabelastisser commentedon Oct 20, 2025
@pac-guerreiro, what's your Upwork profile?
pac-guerreiro commentedon Oct 20, 2025
@isabelastisser I'm not a contributor, there's no need to pay me 😉
melvin-bot commentedon Oct 20, 2025
📣 @pac-guerreiro! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
ZhenjaHorbach commentedon Oct 25, 2025
This issue was demoted and was open for external contributors(#72140 (comment))
And if this were a critical issue, the internal engineer could always assign the original developers
isabelastisser commentedon Oct 29, 2025
UPDATEDPayment summary:@pasyukevich does not require payment (Contractor)
@waterim does not require payment (Contractor)
@pac-guerreiro does not require payment (Contractor)
@ZhenjaHorbach pending in NewDot for C+ review
isabelastisser commentedon Oct 29, 2025
All set!