-
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
[HOLD for payment 2024-07-10] [$250] Workspace - Error page when navigate to Workspace Join link after leaving the workspace #43436
Comments
Triggered auto assignment to @isabelastisser ( |
@isabelastisser FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
ProposalPlease re-state the problem that we are trying to solve in this issue.The not found page is shown when we reopen the workspace join link after leaving it. What is the root cause of that problem?When we successfully leave from a workspace, we still keep the policy object data. It's really weird that the pending action is still App/src/libs/actions/Policy/Policy.ts Lines 649 to 660 in 65db650
When we reopen the join link/page, the condition below detects that the workspace exists, thus we are navigated to the profile page. App/src/pages/workspace/WorkspaceJoinUserPage.tsx Lines 45 to 51 in 65db650
The not found page will be shown if the policy/workspace has a pending action of delete, thus we see the not found page.
What changes do you think we should make in order to solve the problem?First, we should clear the policy data after successfully leaving a workspace.
Next, because not found page will be shown for pending delete workspace, we need to add a new check here to make sure the pending action is not App/src/pages/workspace/WorkspaceJoinUserPage.tsx Lines 45 to 51 in 65db650
We can optionally check for the policy ID. Let me know if we want to do that |
Job added to Upwork: https://www.upwork.com/jobs/~0191daed4e48342857 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @abdulrahuman5196 ( |
@abdulrahuman5196, can you please review the proposal above? Thanks! |
@isabelastisser, @abdulrahuman5196 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@abdulrahuman5196 please review the proposal above. Thanks! |
@abdulrahuman5196, please provide an update. Thanks! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Hi, @isabelastisser I am back now since I was OOO for couple of days as posted in slack. Will work on review today. |
checking now |
Hi @isabelastisser / @bernhardoj , this link is only setting the workspace as ![]() |
@abdulrahuman5196 I use my other account workspace invitation. So, I get my account B workspace join link, account A opens it, and account B accepts the request (in #admins room if I'm not mistaken). |
@isabelastisser @abdulrahuman5196 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! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@abdulrahuman5196, please share an update. Thanks! |
@isabelastisser, @abdulrahuman5196 Huh... This is 4 days overdue. Who can take care of this? |
sorry i didn't update here, the PR was already merged :) |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.3-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 2024-07-10. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@allgandalf, please complete the checklist above. Thanks! |
Just FYI, I will request the payment through ND. |
Regression Test Proposal
Do we agree 👍 or 👎 |
Requested in ND |
Payment summary: @bernhardoj contributor / $250 / pending in NewDot |
@AndrewGable can you please review the regression test proposal? thanks! |
$250 approved for @bernhardoj |
Yes, looks good |
All set! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.81-1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4609575&group_by=cases:section_id&group_order=asc&group_id=229065
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: applause internal team
Slack conversation:
Action Performed:
Expected Result:
User should be able to navigate to the workspace
Actual Result:
Error page when navigate to Workspace Join link after leaving the workspace
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6508578_1718048869729.Recording__3163.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @isabelastisserThe text was updated successfully, but these errors were encountered: