Skip to content

[Due for payment 2025-12-25] Expense - User is marked as selected on recipient list when expense amount is negative #77619

Description

@jponikarchuk

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.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.
  1. Go to staging.new.expensify.com
  2. Open FAB > Create expense > Manual.
  3. Enter amount > Next.
  4. Select any user (not workspace chat).
  5. On confirm page, click RHP back button twice.
  6. Add negative sign to the amount > Next.
  7. Click Next.
  8. 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.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @strepanier03

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions