Expense - Distance rate is reset when editing distance in a distance track expense

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.75-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome
App Component: Money Requests

Action Performed:

1. Open the staging.new.expensify.com website.
2. Open self DM.
3. Tap on the "+" button and select "Track Expense"
4. Select distance and complete the creation flow.
5. Once redirected to chat, tap on "Categorize it"
6. Select any category.
7. Add a merchant.
8. Submit the expense to any workspace.
9. Change the distance rate to be able to send it to workspace.
10. Open the expense report and tap on "Distance"
11. Change any waypoint so the distance and amount are updated.

Expected Result:

After changing the distance of a categorized track expense, the distance rate should remain the same that the user selected when submitting it.

Actual Result:

Distance rate gets reseted and user has to change it again after the distance of the categorized track expense is edited when submitted to a workspace.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6691864_1733988844305.Rate.mp4

View all open jobs on GitHub

[melvin-bot]

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

[RachCHopkins]

Instructions are overly complex and don't appear to reflect reality. There is no merchant on a distance expense. There is no way following this, to not-send it to a workspace immediately, because that's what the Categorise it action does.

There's definitely something funky happening with the distance travelled, but that's not covered here.