Skip to content

[$250] Manual distance - Rate field on confirm page shows default rate instead of last selected rate #71572

Closed

Description

@nlemma

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.2.20-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1030/folder/13176744/41237166/924222990
Email or phone of affected tester (no customers): huhuibshdiushbudish@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Create two workspaces - Workspace A and Workspace B.
  • Each workspace has two distance rates - 0.70 / mile and 1.00 / mile
  1. Go to staging.new.expensify.com

  2. Go to workspace chat A.

  3. Click + > Track distance > Map.

  4. Create a Map distance expense with 1.00 / mile rate.

  5. Click + > Track distance > Map.

  6. Enter waypoints > Next.
    → On confirm page, Rate field shows the last selected rate (1.00 / mile), which is expected.

  7. Go to workspace chat B.

  8. Click + > Track distance > Manual.

  9. Create a Manual distance expense with 1.00 / mile rate.

  10. Click + > Track distance > Manual.

  11. Enter distance > Next.
    → On confirm page, Rate field shows the the default rate (0.70 / mile) instead of the last selected rate (1.00 / mile), which is inconsistent with Step 6 where Map distance is created and Rate field shows the last selected rate (1.00 / mile).

Expected Result:

In Step 11, Rate field will show the last selected rate, which is 1.00 / mile.

Actual Result:

In Step 11, Rate field shows the the default rate (0.70 / mile) instead of the last selected rate (1.00 / mile).

This is inconsistent with Step 6 where Map distance is created and Rate field shows the last selected rate (1.00 / mile).

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

Bug6960127_1759231964300.Screen_Recording_2025-09-30_at_19.31.25.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021973662938595570701
  • Upwork Job ID: 1973662938595570701
  • Last Price Increase: 2026-02-11
Issue OwnerCurrent Issue Owner: @akinwale

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 30, 2025
  2. melvin-bot commented on Sep 30, 2025

    @melvin-bot

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

  3. samranahm commented on Sep 30, 2025

    @samranahm
  4. samranahm commented on Sep 30, 2025

    @samranahm
    Contributor

    BE return wrong customUnitRateID for Manual track distance and that id's rate match with defaultMileageRate causing this bug.

  5. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Oct 2, 2025
  6. changed the title [-]Manual distance - Rate field on confirm page shows default rate instead of last selected rate[/-] [+][$250] Manual distance - Rate field on confirm page shows default rate instead of last selected rate[/+] on Oct 2, 2025
  7. melvin-bot commented on Oct 2, 2025

    @melvin-bot
  8. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Oct 2, 2025
  9. melvin-bot commented on Oct 2, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @akinwale (External)

  10. melvin-bot commented on Oct 9, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  11. melvin-bot commented on Oct 13, 2025

    @melvin-bot

    @akinwale 10 days overdue. I'm getting more depressed than Marvin.

  12. 26 remaining items

  13. mvtglobally commented on Dec 13, 2025

    @mvtglobally

    Issue not reproducible during KI retests. (Second week)

  14. melvin-bot commented on Dec 18, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  15. melvin-bot commented on Dec 25, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  16. melvin-bot commented on Jan 1, 2026

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  17. mvtglobally commented on Jan 3, 2026

    @mvtglobally

    Issue not reproducible during KI retests. (Third week)

  18. melvin-bot commented on Jan 8, 2026

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  19. melvin-bot commented on Jan 21, 2026

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  20. melvin-bot commented on Jan 28, 2026

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  21. melvin-bot commented on Feb 4, 2026

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  22. melvin-bot commented on Feb 11, 2026

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  23. melvin-bot commented on Feb 13, 2026

    @melvin-bot

    @akinwale, @dylanexpensify, this Monthly task hasn't been acted upon in 6 weeks; closing.

    If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsMonthlyKSv2Not a priority

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions