-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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 2025-02-27] [$250] Bug: Going back and forth on multi connection page displays a disconnect prompt. #56385
Comments
Current assignee @s77rt is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to @greg-schroeder ( |
Didn't look into this yet |
@yuwenmemon, @s77rt, @greg-schroeder Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Will look into this today |
Fix #56702 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.1-6 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-02-27. 🎊 For reference, here are some details about the assignees on this issue:
|
@s77rt @greg-schroeder @s77rt 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] |
No checklist is needed. This is a follow up from NSQS PR #55049 |
Payment Summary
BugZero Checklist (@greg-schroeder)
|
@greg-schroeder Payment for NSQS will be handled after the NSQS project is complete. However we should pay @DylanDylann as he reviewed the PR. |
I'm going to make this |
|
Job added to Upwork: https://www.upwork.com/jobs/~021895123531434085041 |
Current assignee @s77rt is eligible for the External assigner, not assigning anyone new. |
Offer sent to @DylanDylann for reviewer role! |
Paid |
Bug; If you try to connect using the multi-connection page then go back and forth again, the disconnect prompt is always re-displayed.
Screen.Recording.2025-01-21.at.10.25.12.AM.mov
Fix attempt 1 (from @s77rt): If I force going back to the correct route (without the integrationToDisconnect params, etc.), the bug is fixed but the navigation direction is not correct.
Screen.Recording.2025-01-21.at.10.28.27.AM.mov
Issue Owner
Current Issue Owner: @Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: