Skip to content

[Odometer] [Tracking] Add Odometer mileage to NewDot #71841

Closed

Description

@Julesssss

DESIGN DOC ➡️

Slack Room: #migrate

Implementation issues:

Main Flow Phase 1: Add Odometer expense type

Bugs/Improvements:

Main Flow Release 2: Add 'Save for later' feature

Bugs/Improvements:

Related:

Proposal

Add Odometer mileage expenses to NewDot

Background

Expensify is completing the migration from Classic to NewDot. Feature parity is essential for retaining users during this migration, and odometer tracking is one of the few remaining blockers to achieving this. Manual odometer tracking is necessary for users who prefer explicit control over mileage entries rather than automatic GPS tracking, particularly for those who drive frequently for work and need precise records for tax purposes and reimbursement.

Problem

When users track distance expenses via odometer readings in Classic, if they are migrated to NewDot, then they must either manually calculate total distance (losing odometer proof and audit trail) or abandon NewDot to stay in classic or switch to a competing application.

Solution

Introduce odometer mileage as a distance tracking method in NewDot with feature parity to Classic. Users will be able to:

  • Select the new Odometer tab in the Track Distance page
  • Manually enter start and end mileage readings
  • Attach photos of each reading
  • View calculated odometer readings and submit as a distance expense

For compatibility and parity, the feature will use the same NVP storage approach (odometerStart, odometerEnd) and validation logic (preventing negative distances, requiring both readings for submission) as Classic.

Tasks

  • Post Proposal (full Problem/Solution statement) in #whatsnext
  • Wait at least one full business day, and until the post has a majority (2/3) of positive reactions (👍)
  • Paste Proposal in the space above with a link to the Slack thread
  • Email strategy@expensify.com and paste in the Proposal
  • Host a pre-design meeting (example) in an appropriate slack channel to discuss any necessary details in public before filling out the High-level of proposed solution section.
  • Fill out the High-level overview of the problem, Timeline, Terminology, and High-level of proposed solution sections of the Design Doc
  • Email strategy@expensify.com (continue the same email chain as before - your last message should be the WN Proposal) with the link to your Design Doc containing your high-level problem and solution
  • Add the DesignDocReview label to get the High-level overview of the problem and High-level of proposed solution section reviewed
  • Respond to any questions or concerns and bring up blockers in Slack to get a consensus if necessary
  • Confirm that the doc has the minimum necessary number of reviews before proceeding
  • Host another pre-design meeting in the appropriate slack channel to ask for engineering feedback on the technical solution.
  • Fill out the Detailed implementation of the solution and related sections.
  • Re-add the DesignDocReview label to this issue
  • Respond to any questions or concerns and bring up blockers in Slack to get consensus if necessary
  • Confirm that the doc has the minimum necessary number of reviews before proceeding
  • Email strategy@expensify.com one last time to let them know the Design Doc is moving into the implementation phase
  • Implement the changes
  • Add regression tests so that QA can test your feature with every deploy (instructions)
  • Confirm any related help site updates have been published
  • Send out a follow up email to strategy@expensify.com once everything has been implemented and do a Project Wrap-Up retrospective that provides:
    • Summary of what we accomplished with this project
    • What went well?
    • What could we have done better?
    • What did we learn?

Activity

  1. self-assigned this
    on Oct 3, 2025
  2. melvin-bot commented on Oct 14, 2025

    @melvin-bot

    Triggered auto assignment to @VictoriaExpensify (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO. Remember to draft any necessary HelpDot updates by following the instructions here.

  3. melvin-bot commented on Oct 14, 2025

    @melvin-bot

    ⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️

  4. melvin-bot commented on Oct 14, 2025

    @melvin-bot

    Triggered auto assignment to Design team member for new feature review - @shawnborton (NewFeature)

  5. changed the title [-][Placeholder] Add Odometer milage to NewDot[/-] [+][Tracking] Add Odometer milage to NewDot[/+] on Oct 14, 2025
  6. 156 remaining items

  7. Julesssss commented on Apr 21, 2026

    @Julesssss
    ContributorAuthor

    The feature is live and in use by customers! Phase 2 PRs are in progress.

    Going ooo for surgery and recovery, I'll send the wrap up for phase one once I'm back.

  8. Julesssss commented on Apr 27, 2026

    @Julesssss
    ContributorAuthor

    PR to implement 'Save for Later' and resolve 2 bugs is in draft, nearing review.

  9. Julesssss commented on May 5, 2026

    @Julesssss
    ContributorAuthor

    'Save for Later' feature PR has had some bugs fixed, back in review

  10. Julesssss commented on May 5, 2026

    @Julesssss
    ContributorAuthor

    Release 2 is essentially complete as the Save for Later feature is merged 🎉 We raised a last bug related to splits

  11. Julesssss commented on May 7, 2026

    @Julesssss
    ContributorAuthor

    Odometer release 2 is live on production. Expense drafts can now be persisted and retrieved.

    • Save for later PR
    • Help site update PR for Save for later feature
  12. Julesssss commented on May 8, 2026

    @Julesssss
    ContributorAuthor

    Remaining tasks:

    1. Release 2 Help docs PR needs resource update review
    2. Release 2 test cases need to be added to QA regression tests
    3. Send wrap up email
  13. Julesssss commented on May 11, 2026

    @Julesssss
    ContributorAuthor

    The project is officially complete 🎉 🚗

    • New test cases added by QA
    • Help doc PR merged
    • Wrap up email sent 📨
  14. Julesssss commented on May 15, 2026

    @Julesssss
    ContributorAuthor

    Finishing up issues outside of this tracker.

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

Metadata

Metadata

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions