Skip to content

Report - Amount field accepts 0 amount in IOU expense when inline editing #88640

Closed

Description

@lanitochka17

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.62-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #83127
Email or phone of affected tester (no customers): jnsdijsnodjonjiosjdio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Open 1:1 DM with any user.
  3. Create two manual expenses.
  4. Open the report.
  5. Click Amount field.
  6. Enter 0 and save it.

Expected Result:

Amount field should not accept 0 amount in IOU expense.

Actual Result:

Amount field accepts 0 amount in IOU expense when inline editing.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7136939_1776975845456.7.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @ahmedGaber93

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 23, 2026
  2. melvin-bot commented on Apr 23, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #83127

  3. melvin-bot commented on Apr 23, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  4. github-actions commented on Apr 23, 2026

    @github-actions
    Contributor

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

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. trjExpensify commented on Apr 23, 2026

    @trjExpensify
    Contributor

    This is valid for an expense on an expense report. I can understand why it's not on an iou report because you wouldn't request nothing from someone in a P2P capacity. That said, as it's an iou bug, I'd be okay with demoting it. What do you think, @puneetlath?

    CC: @ahmedGaber93 for vis

  6. ahmedGaber93 commented on Apr 23, 2026

    @ahmedGaber93
    Contributor

    Ahh, this is a subcase for IOU that we missed handling. CC @mohammadjafarinejad

  7. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 24, 2026
  8. melvin-bot commented on Apr 27, 2026

    @melvin-bot

    @puneetlath Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  9. puneetlath commented on Apr 28, 2026

    @puneetlath
    Contributor

    Added to #88711

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions