You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-06-05] [$50] When editing distance on confirm page & select different user, old amount & distance are shown #62444
Version Number: 9.1.47-5 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail: Exp Email or phone of affected tester (no customers):sddsnsduhisudh2@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.4 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Account has self DM.
Go to staging.new.expensify.com
Go to self DM.
Track a distance expense.
Click Submit it to someone.
Select a user.
On confirmation page, click Distance.
Edit the waypoints and save it.
Click app back button to go back to Share list.
Select another user.
Note that the new amount and distance are shown on the confirmation page.
Click app back button.
Select the same user from Step 9.
Expected Result:
The new amount and distance are shown on the confirmation page after selecting a different user (production behavior).
Actual Result:
The original amount and distance are shown on the confirmation page.
👋 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:
Identify the pull request that introduced this issue and revert it.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.53-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@dukenv0307@strepanier03@dukenv0307 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Aaah, got it. So no paymen,t but how about a reg test @dukenv0307? Will we need to make one of those? If not, then let's close this otherwise we can keep it open until the reg test steps are added, and I can finish up the GH for that.
Activity
melvin-bot commentedon May 21, 2025
Triggered auto assignment to @strepanier03 (
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.melvin-bot commentedon May 21, 2025
Triggered auto assignment to @mollfpr (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 21, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 21, 2025
👋 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:
mollfpr commentedon May 21, 2025
@mitarachim I can't reproduce the issue. Could you test again? Thanks!
mitarachim commentedon May 21, 2025
Hello @mollfpr , i still could reproduce this issue using build v9.1.47-5
Screen.Recording.2025-05-21.at.3.12.35.PM.mov
32 remaining items
melvin-bot commentedon May 29, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.53-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-06-05. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 29, 2025
@dukenv0307 @strepanier03 @dukenv0307 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
melvin-bot commentedon Jun 5, 2025
Payment Summary
Upwork Job
BugZero Checklist (@strepanier03)
strepanier03 commentedon Jun 5, 2025
@dukenv0307 - Wanna finish up the checklist? When I make the reg test, I'll remove the hold from the payment summary below.
strepanier03 commentedon Jun 5, 2025
@dukenv0307 @VickyStash -- Actually, the GH title says $50 and the payment comment says $250? Anyone have context on that they can share?
dukenv0307 commentedon Jun 6, 2025
@strepanier03 I think we can do nothing here because it's our regression.
melvin-bot commentedon Jun 9, 2025
@strepanier03 Whoops! This issue is 2 days overdue. Let's get this updated quick!
strepanier03 commentedon Jun 9, 2025
Aaah, got it. So no paymen,t but how about a reg test @dukenv0307? Will we need to make one of those? If not, then let's close this otherwise we can keep it open until the reg test steps are added, and I can finish up the GH for that.
dukenv0307 commentedon Jun 9, 2025
@strepanier03 i think we can close it
strepanier03 commentedon Jun 10, 2025
Thanks @dukenv0307 feel free to reopen or ping me in Slack if anything changes.