Skip to content

[Due for payment 2025-10-17] [$250] Cannot make an expense negative #53441

Closed
1 of 1 issue completed
Closed

Description

@m-natarajan

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.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:

  1. SmartScan a receipt
  2. Open the expense
  3. Open the amount
  4. 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?

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Shottr 2024-12-03 10 02 13

Recording.815.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021866173019746429432
  • Upwork Job ID: 1866173019746429432
  • Last Price Increase: 2025-01-11
  • Automatic offers:
    • ZhenjaHorbach | Reviewer | 105292850
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @isabelastisser

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    and removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 3, 2024
  2. melvin-bot commented on Dec 4, 2024

    @melvin-bot

    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.

  3. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Dec 9, 2024
  4. changed the title [-]Cannot make an expense negative[/-] [+][$250] Cannot make an expense negative[/+] on Dec 9, 2024
  5. melvin-bot commented on Dec 9, 2024

    @melvin-bot
  6. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Dec 9, 2024
  7. melvin-bot commented on Dec 9, 2024

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @ZhenjaHorbach (External)

  8. 327 remaining items

  9. isabelastisser commented on Oct 20, 2025

    @isabelastisser
    Contributor

    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 👎

  10. ZhenjaHorbach commented on Oct 20, 2025

    @ZhenjaHorbach
    Contributor

    Oh
    It was a long issue
    I already forgot that I started it on Upwork
    And now I'm getting a payment on ND 😅

  11. isabelastisser commented on Oct 20, 2025

    @isabelastisser
    Contributor

    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

  12. isabelastisser commented on Oct 20, 2025

    @isabelastisser
    Contributor

    @pac-guerreiro, what's your Upwork profile?

  13. pac-guerreiro commented on Oct 20, 2025

    @pac-guerreiro
    Contributor

    @isabelastisser I'm not a contributor, there's no need to pay me 😉

  14. melvin-bot commented on Oct 20, 2025

    @melvin-bot

    📣 @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:

    1. Make sure you've read and understood the contributing guidelines.
    2. 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.
    3. 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.
    4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
      Screen Shot 2022-11-16 at 4 42 54 PM
      Format:
    Contributor details
    Your Expensify account email: <REPLACE EMAIL HERE>
    Upwork Profile Link: <REPLACE LINK HERE>
    
  15. ZhenjaHorbach commented on Oct 25, 2025

    @ZhenjaHorbach
    Contributor

    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

  16. isabelastisser commented on Oct 29, 2025

    @isabelastisser
    Contributor

    UPDATED Payment 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

  17. isabelastisser commented on Oct 29, 2025

    @isabelastisser
    Contributor

    All set!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions