Expense - Negative amount is not saved when merging track expense with workspace expense

[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: v9.2.15-1 PR:65001
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exploratory #65001
Email or phone of affected tester (no customers): jsdoinjosdjosjniosdj@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: undefined

Action Performed:

Precondition:

• Account has self DM and workspace.

1. Go to 65001.pr-testing.expensify.com
2. Go to workspace chat.
3. Create an expense with negative amount.
4. Go to self DM.
5. Create a track manual expense.
6. Open the track expense.
7. Click More > Merge.
8. Select the expense from Step 3 with negative amount.
9. Click Continue.
10. Select the negative amount for Amount section.
11. Select any detail for the other sections > Click Continue.
12. Click Merge expenses.

Expected Result:

The negative amount will be saved because it was selected in Step 8 during merging.

Actual Result:

The negative amount is not saved despite selecting it in Step 8 during merging.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @pasyukevich

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @Beamanator (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

[ZhenjaHorbach]

This isn't a deploy blocker
It's just part of testing the PR, which is still under development