-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Change _Submit Debug Logs_ dialog not to require GitHub issue #28394
Comments
We don't look through rageshakes unless they are linked to a github issue we are triaging, so you can send them, but unless one of the devs asked you to, they won't be looked at so might as well be going into the abyss. Not changing this as it is as designed. |
It's been fun to be a messenger between you, guys. Keep on the good work! |
This is not a direct quote, to be clear. |
I don't agree. Plenty of rageshakes do get looked at; in particular they are an extremely valuable resource for investigating and triaging sources of UTD errors. My experience is that people are deterred from submitting debug reports due to this text. I agree that it's time for this text to be reconsidered. |
I have been told by Product & my manager to not spend any further time on investigating rageshakes unless they concern an issue we are looking at since at least 12 months ago. It used to be part of the triage rota but no longer. So whilst some other teams might periodically look at them, there is zero guarantee that the rageshake is not going into the abyss, especially when it doesn't concern the failure mode that team is interested in (e.g. UTDs in this case) |
no disagreement with that. Just hoping we can reword the dialog to be slightly less off-putting. Let's discuss in tomorrow's call. |
The dialog as it stands was implemented to match designs, this isn't something we should be going behind their back on |
Description
Right now Submit Debug Logs contain only this:
According to @richvdh the text should read something like that:
Outcome
Inexperienced users cannot simply report UTD problems, for example, while they are really suggested to do so.
The text was updated successfully, but these errors were encountered: