-
Notifications
You must be signed in to change notification settings - Fork 3
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
INVITATIONS: User has to click Join Topic twice after clicking View without joining (Sub-issue of #1376) #1900
Labels
bug
Something isn't working
HOLD in pre-live
Issues in pre-live that should *not* yet be released to production
Story of Estonia
Issues needing implementation before Story of Estonia launch
Comments
@BeccaMelhuish it happens in group as well (see screen recording) Screen.Recording.2025-02-19.at.17.45.49.mov |
OK, thank you - I'll keep pre UX tests label then and but remove UX priority label. Not ideal to not have it ready for the user tests (no one will click the join button I'm sure), but if we can't, then so be it :) |
Removing pre-UX tests label for this one as had misunderstood the issue, less important than I had thought :) |
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
HOLD in pre-live
Issues in pre-live that should *not* yet be released to production
Story of Estonia
Issues needing implementation before Story of Estonia launch
What is the problem?
Tested in Dev Environment in Google Chrome
A user is invited to a public topic and clicks on View topic without joining (screenshot1) and clicks on Join Topic (screenshot2). They are prompted to login (screenshot3), and after successfully logging in, they are not automatically joined to the topic but have to click Join Topic once again (screenshot4).
Why is this a problem?
User has to click the same button twice which is confusing
Possible solution.
@DiverVM @BeccaMelhuish from what I understand, the user should have 'Joined' topic status after they have successfully logged in?
I think Viktor is aware of this issue, so going to put it in "in progress".
The text was updated successfully, but these errors were encountered: