[sleepybrett]

He's saying, and I agree, that a casual first time user making a low friction complaint somewhere like here should simply be digested immediately by a team member and ammended onto a perviously created bug in their system. Or a new bug should be created by a team member.

I do this at my job all the time because our Jira setup is fucking balls and I have all kinds of greesemonkey to make it usable and quick for me. Any casual user is going to bounce the fuck off our jira setup. Secondly I know if there is already a bug in our system covering this issue or not, less time for my team to do de-duping etc.

[vlovich123]

Yup. About the only two complaints that might reasonably warrant asking the user to create a ticket themselves is the NAT one and the CPU spike doing nothing. For both of those though, rather than having the user create a bug report just to go back and forth over it asynchronously over months until the end user gets discouraged and drops it, a better situation works be diagnostic tools that could monitor and collect data that the devs could then analyze, ideally baked into the code where you just click a button to submit feedback and your code can code to open a bug report or just ingest metrics or something.