Repository navigation
Description
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.13-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #80916
Email or phone of affected tester (no customers): jsoidjnosidnjodsjiosd@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:
- Go to staging.new.expensify.com
- Go to workspace chat.
- Create an expense with amount 10.00.
- Open the expense report.
- Click More > Split > Save.
- Open any split.
- Click Amount.
→ Edit splits header shows the original amount - 10.00. - Change one of the split amounts to 1.00 and click Save.
- Open any split.
- Click Amount.
Expected Result:
After editing split amount, Edit splits header will show the original amount which is 10.00.
Actual Result:
After editing split amount, the original amount in Edit splits header changes to 6.00, which means user can no longer edit the splits back to 5.00 amount each.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
Screenshots/Videos
Bug7068713_1770323559102.2.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~022019515180703035337
- Upwork Job ID: 2019515180703035337
- Last Price Increase: 2026-02-05
Issue Owner
Current Issue Owner: @mallenexpensifyMetadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
melvin-bot commentedon Feb 5, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #80916
[-]Expense - Original amount is not retained after editing split amount[/-][+][$250] Expense - Original amount is not retained after editing split amount[/+]melvin-bot commentedon Feb 5, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022019515180703035337
melvin-bot commentedon Feb 5, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Feb 5, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @dukenv0307 (
External)melvin-bot commentedon Feb 5, 2026
Triggered auto assignment to @NicMendonca (
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.24 remaining items
ZhenjaHorbach commentedon Feb 9, 2026
Thanks!
melvin-bot commentedon Feb 26, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Mar 5, 2026
This issue has not been updated in over 15 days. @NicMendonca, @mollfpr, @dukenv0307 eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
melvin-bot commentedon Mar 17, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Mar 17, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
dominictb commentedon May 1, 2026
@dukenv0307 Are you due payment here?
ZhenjaHorbach commentedon May 1, 2026
I suppose we can close this
dukenv0307 commentedon May 1, 2026
yes, we can close this
mallenexpensify commentedon May 1, 2026
Is anyone due payment? Do any other issues need to be updated to denote a regression (don't think so)
Seems like a weird one.....