Skip to content
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

Can't submit a bug report without registering #4802

Closed
turt2live opened this issue Aug 16, 2017 · 3 comments
Closed

Can't submit a bug report without registering #4802

turt2live opened this issue Aug 16, 2017 · 3 comments
Labels
P2 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@turt2live
Copy link
Member

turt2live commented Aug 16, 2017

Description

You're prompted several times and eventually give up. If there's a problem with the registration process, or with something in the context of an unregistered user, it's really hard to submit a bug report.

Note: This was submitted to me through another user on a not-matrix.org homeserver. Their issue was human error, but they were frustrated that they couldn't rageshake their problem on web

Steps to reproduce

  • Don't be logged in
  • Try to submit a bug report

Expectation: Being able to send a bug report without having to go through the registration process.

Log: not sent

Version information

  • Platform: web (in-browser)
  • Browser: Chrome 59
  • OS: Windows 10
  • URL: riot.im/develop
@lampholder
Copy link
Member

Because:

  • filing a bug lives in the user settings panel
  • we made a decision during ILAG that opening the user settings panel would launch the 'pick a username' dialogue

It strikes me that:

  • only users familiar with Riot will be looking for the ability to file a bug behind user settings (so only they will be frustrated by its being inaccessible without registration)
  • anyone who is hit by a bug during registration (or login for that matter) will not be able to make us aware of that fact without herculean effort on their part (so we'll be missing vital data)

I'm going to make this a P2 because it seems like a risky gap but we don't have any suggestion of catastrophic registration bugs today.

Also, it's an interesting design challenge - how would we implement the UX to ingest maximum useful bug reporting?

@lampholder lampholder added T-Defect design S-Major Severely degrades major functionality or product features, with no satisfactory workaround P2 labels Aug 16, 2017
@turt2live
Copy link
Member Author

turt2live commented Aug 16, 2017

In general, most people would be aware of Riot enough to get a registration bug to the Riot team. In this case, it just so happened to be that they didn't know what Riot was but wanted to get help and ended up reaching out to me as I'm the point of contact for stuff like this in our organization.

Note: I understand we're a rare case here, just wanted to clarify the motivation for the ticket

turt2live added a commit that referenced this issue Nov 27, 2018
This is mostly useful for cases when the UI is broken or the user can't access the button because they aren't logged in. This is particularly helpful for troubleshooting issues with .well-known discovery if/when they come up.

Ref: #4802
@turt2live
Copy link
Member Author

I'm going to consider this fixed by #7755

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

2 participants