-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLDING on #26538][$500] Distance - Changing stop and finish causes TDB in distance #28566
Comments
Triggered auto assignment to @johncschuster ( |
Job added to Upwork: https://www.upwork.com/jobs/~01ce183a2973a17c45 |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.App displays TBD in amount and in miles and also does not display route if we exchange stop and finish values What is the root cause of that problem?After we select the workspace in the participants page, we set the money request id with the report id of the workspace here. But later when we navigate back to the Distance selection page, we don't use that reportID in the param. So in here, it will reset all the money request data. Leading to the What changes do you think we should make in order to solve the problem?We need to add the reportID to the route params when navigating back from the participants page to the distance page. So it will be considered editing a draft money request, not creating (and resetting) a new money request. What alternative solutions did you explore? (Optional)NA |
The RCA is the same as in #28129 - there was a little discussion in the original slack thread. |
ref: #26946 (comment) |
@johncschuster should we post this on Hold? Based on the previous comments and linked one, we should hold all |
Sounds good, @mananjadhav! I've just put it on hold. |
@mananjadhav, @johncschuster Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Still holding |
Still holding |
@mananjadhav @johncschuster this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Issue not reproducible during KI retests. (First week) |
That's great! We'll keep this open one more week and see if the behavior is reproducible during the next KI tests. |
@mananjadhav @johncschuster this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks! |
@mvtglobally can you check to see if this behavior is still reproducible? |
@mvtglobally bump! |
Updating shortly |
Issue not reproducible during KI retests. (Second week) |
@mananjadhav @johncschuster @mvtglobally this issue is now 4 weeks old and preventing us from maintaining WAQ, can you:
Thanks! |
Current assignee @mananjadhav is eligible for the Internal assigner, not assigning anyone new. |
@mananjadhav, @johncschuster, @mvtglobally Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@mananjadhav, @johncschuster, @mvtglobally Huh... This is 4 days overdue. Who can take care of this? |
@mananjadhav it looks like this behavior might not be reproducible anymore. I'm going to close this issue unless you feel differently. |
@johncschuster Be sure to fill out the Contact List! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
App should modify amount and miles and route if we exchange stop and finish values
Actual Result:
App displays TBD in amount and in miles and also does not display route if we exchange stop and finish values
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.75-8
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
ios.native.TBD.for.replacing.stop.and.finish.mov
android.native.TBD.for.replacing.stop.and.finish.mov
ios.safari.TBD.for.replacing.stop.and.finish.mov
android.chrome.TBD.for.replacing.stop.and.finish.mp4
windows.chrome.TBD.for.replacing.stop.and.finish.mp4
mac.chrome.TBD.for.replacing.stop.and.finish.mov
mac.desktop.TBD.for.replacing.stop.and.finish.mov
Recording.120.mp4
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1696063336006619
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mvtgloballyThe text was updated successfully, but these errors were encountered: