Expense - No error shows up when 0.00 amount when bulk editing invoice expenses

[mitarachim]

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.3.34-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: #82948
Email or phone of affected tester (no customers): jdofinjdoinjidfojdo@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:

Precondition:

• Enable Invoices.

1. Go to staging.new.expensify.com
2. Open FAB > Send invoice.
3. Send an invoice to any user.
4. Send another invoice to the same user.
5. Go to Reports > Expenses.
6. Click Type > Invoice > Apply.
7. Bulk select both expenses.
8. Click dropdown button > Edit multiple.
9. Click Amount.
10. Enter 0 and save it.
11. Click Save.

Expected Result:

Error will show up when saving 0.00 amount when bulk editing invoice expenses because 0.00 amount is not allowed when sending/editing invoice.

Actual Result:

No error shows up when 0.00 amount when bulk editing invoice expenses.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7098319_1773098199672.9.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @laurenreidexpensify (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.

[github-actions]

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