Distance - Original and Removed commuter distance shows new exclusion instead of edited distance

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.52-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: #93848
Email or phone of affected tester (no customers): applausetester+ssndjois2jd1@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Log in with Expensifail account.
• Enable Distance rates.
• Enable "Exclude a fixed distance per claim" in distance settings with 1 miles.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create a map distance expense.
4. Go to workspace settings > Distance rates.
5. Click Settings > Exclude commutes.
6. Edit Exclude a fixed distance per claim" to 20 miles (the distance should be larger than the created distance expense in Step 3).
7. Go back to workspace chat and open the expense.
8. Click Distance.
9. Edit distance and save it.

Expected Result:

Original and Removed commuter distance should show the correct edited distance.

Actual Result:

Original and Removed commuter distance shows the new exclusion instead of the correct edited distance.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7230734_1786424280355.24.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7230734

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/1e52637b9e86f98c9d2554f7338783994fb1c75cb3e3fb38e1e3d9a8a51d8749

https://platform.applause.com/services/links/v1/external/e557d709722f29db71336126ef86601a0dfb20550e4ef48757c3715365484c7f

[melvin-bot]

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

[melvin-bot]

@Gonals @marufsharifi you have been assigned to this deploy blocker because you reviewed the offending PR: #93848

[melvin-bot]

@fedirjh you have been assigned to this deploy blocker because you authored the offending PR: #93848

[melvin-bot]

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

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