-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2023-10-09] [$500] [Distance] - Ability to request money without filling start and finish points #27383
Comments
ProposalPlease re-state the problem that we are trying to solve in this issue.[Distance] Ability to request money without filling start and finish points What is the root cause of that problem?We don't allow user to back to the first step if the request is a distance request App/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsPage.js Line 66 in 4d104f5
App/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsPage.js Line 78 in 4d104f5
What changes do you think we should make in order to solve the problem?We should remove the check What alternative solutions did you explore? (Optional) |
Job added to Upwork: https://www.upwork.com/jobs/~01bf360a8a0ff38420 |
Triggered auto assignment to @joekaufmanexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to @tjferriss ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Ability to request money without filling start and finish points What is the root cause of that problem?App/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsPage.js Lines 79 to 81 in 7deca7a
App/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsPage.js Lines 67 to 69 in 7deca7a
Let's see this code, we only navigate back if itn't distance request. It seems that we want to prevent user come back in distance request What changes do you think we should make in order to solve the problem?We should update the logic to allow users:
To do that we can get waypoint from transaction like this
and in here App/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsPage.js Lines 79 to 81 in 7deca7a
App/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsPage.js Lines 67 to 69 in 7deca7a
update the condition to
instead of only What alternative solutions did you explore? (Optional)Same like the main solution but we can use isEmptyRoute instead of isEmptyWaypoint
|
@tjferriss I'll grab this one as you were the second assignee, and this issue doesn't need two BZ assignees. |
Reproduced and agreed that this is a bug. Makes sense to me that we'd just redirect back to https://staging.new.expensify.com/request/new/distance, as that's what we seem to do for manual and scan in this same exact scenario. CC @neil-marcellini in case you have thoughts on this. |
Proposals pending review. |
Same |
@allroundexperts Could you please take a look at the proposals on this issue? TY! |
Thanks for your proposal @dukenv0307. In this case, I think its more safer to redirect the user back based on waypoints rather than the amount. This is also what we use when deciding to fetch a route (so its better for consistency as well). As such, I think @DylanDylann's proposal is better. 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @roryabraham, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Great, ty! Changing this to weekly then in the meantime. |
Still held |
Held |
Same |
Follow up PR is merged and should be deployed this week! |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
@allroundexperts I see the PR this one was held on got deployed. We can make more progress on this now. Is that right? |
Yep, we can proceed now. I'm not sure if the second PR caused the regression or not. @DylanDylann Can you please confirm? |
@allroundexperts Yep, but It seems the regression is fixed by another PR |
Okay. So it seems this caused 2 regressions. So just a note that the payment should be 1/4. |
@allroundexperts The first regression is not caused our PR. You can check this comment for more detail |
Gotcha so half it is then! |
Got it. And #28308 was the only thing remaining for this issue, so we're good to do BZ checklist now, issue payment (after 7 day hold) and close? |
Correct @joekaufmanexpensify. |
Sweet. Mind taking care of your portion of the BZ checklist? |
Checklist
Regression Test
Verify that you are redirected to the new distance request page. Do we 👍 or 👎 ? |
Great, ty! BZ checklist is all set. |
All set to issue payment. There was a regression here, so the county due here is:
|
@DylanDylann $250 sent and contract ended! |
Upwork job is closed, so opened new one to pay @hichamcc: https://www.upwork.com/jobs/~01282aaf23d83dd5cc |
@hichamcc offer sent for $50! |
@allroundexperts could you please request $250 via NewDot and confirm here once done? |
@hichamcc $50 sent and contract ended! |
$250 payment approved for @allroundexperts based on this comment. |
Great! Closing as this is all set. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
The app should redirect the user to https://staging.new.expensify.com/request/new/distance
Actual Result:
The app allows users to request money
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.69.0
Reproducible in staging?: y
Reproducible in production?: y
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
participants-bug.webm
Recording.4449.mp4
Expensify/Expensify Issue URL:
Issue reported by: @hichamcc
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694429194889109
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: