[Due for payment 2026-06-30] Add stop address editing for GPS mileage

@mallenexpensify

Problem
When an employee creates a GPS mileage expense, if the recorded trip has an inaccurate stop destination (e.g., forgot to stop), then they have to recreate the expense using manual mileage or a re-drawn map route, which is harder to reproduce accurately and provides weaker supporting documentation for approvers and auditors.

Solution
In one release, we will:

Make the stop address a push row
Show an “Edit stop” page, with a map and a slider below
Users can drag the slider to decrease the distance, which is animated on the map
Where ever the users stops the slider and confirms, we save that stop address when creating the expense (and updating the mileage receipt).

Further details

We'll start saving GPS way points in the BE, which means storing the gpsCoordinates in the commentNVPs (where we currently store existing distance data like routeImageURL and odometer readings).
We'll also start saving any mileage decreases via modifiedDistance, similar to modifiedCreated, modifiedAmount, modifiedMerchant and modifiedMCC.

This is an internal initiative, so we won't open it up to proposals

Issue Owner

Current Issue Owner: @mallenexpensify

@dannymcclain

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

@JmillsExpensify

This issue has not been updated in over 15 days. @JmillsExpensify, @shawnborton, @neil-marcellini, @GCyganek, @dukenv0307, @dominictb 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!

@mallenexpensify

Triggered auto assignment to @mallenexpensify (Awaiting Payment)

@MelvinBot

@MelvinBot please review the compensation request above and provide feedback

Recommendation: The $500 request looks reasonable and well-supported — the only open item is confirming the regression attribution, which dukenv0307 has already asked neil-marcellini to verify.

Here's what I was able to confirm against the request:

2 PRs / ~1k changes ✅ — dukenv0307 was the C+ reviewer on both PRs. Use custom compass on the maps #93026 (74 changed lines, 17 files) and [GPS] Update user location on GPS screen when there is no active GPS trip #91418 (959 changed lines, 22 files) total ~1,033 line changes across 39 files, matching the "2 PRs" and "~1k changes" claims. $500 is consistent with the standard ~$250 C+ review applied per PR.
Test coverage (5 scenarios) — can't independently verify the count, but it's plausible for two PRs of this scope.
Regression dispute ✅ (their claim holds up) — Deploy blocker [Due for payment 2026-08-19] GPS - Edited GPS distance is different on confirm page. #97488 (edited GPS distance differs on the confirm page) was attributed to PR [GPS] Add stop address editing #90002, which is not one of the PRs in this request. So the 50% regression penalty shouldn't apply to the Use custom compass on the maps #93026 / [GPS] Update user location on GPS screen when there is no active GPS trip #91418 compensation here.

One thing to double-check before paying: PR #90002 links to both this issue (#85802) and #95060, and #95060 is its own Awaiting Payment job. So please confirm regression #97488 is being charged against #95060's payment (not this one) — that's the confirmation dukenv0307 is asking neil-marcellini for. Once he confirms, this request looks good to approve at $500.

Compensation is ultimately at Expensify's discretion — this is just a fact-check of the request, not an approval.

view run

@dukenv0307

Payment Summary

Contributor+: @dukenv0307 due $500 via NewDot

cc @neil-marcellini , comment/reopen if you disagree.

@dukenv0307

Approved $500 to @dukenv0307

For the record: #91418 caused an issue where the map didn't update the location after reconnecting. Fixed by #101345.

Navigation Menu

Repository navigation

[Due for payment 2026-06-30] Add stop address editing for GPS mileage #85802

111 remaining items

Payment Summary

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[Due for payment 2026-06-30] Add stop address editing for GPS mileage #85802

Description

Activity

melvin-bot commented on Mar 19, 2026

111 remaining items

melvin-bot commented on Aug 13, 2026

melvin-bot commented on Aug 20, 2026

mallenexpensify commented on Aug 20, 2026

MelvinBot commented on Aug 20, 2026

mallenexpensify commented on Aug 20, 2026

Payment Summary

quinthar commented on Sep 2, 2026

QichenZhu commented on Oct 8, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions