Slashdot Mirror

← Back to Stories (view on slashdot.org)

How Do You Get Better Bug Reports From Users?

Posted by samzenpus on from the that's-a-feature dept.

itwbennett writes "You can try to train them, you can try to streamline or automate the process, you can demand that all bug reports go through a middleman (i.e., a QA tester) or you can throw up your hands and accept that users will forever submit bug reports that in no way help you solve the problem. Like the stages of grief, you've probably tried or experienced all of these at some point. But have you found any approach that really works for getting useful bug reports from your users?"

1 of 205 comments (clear)

  1. Re:Follow up by ccguy · · Score: 5, Insightful

    Requiring a user, after the fact, to recall an error message is futile. They simple have seen to many varied ones and their brain goes 'oh an error message' not 'oh a 504 error' or 'oh a invalid data type error'.

    Believe it or not a user that doesn't remember the error message is not the worst kind of user.

    I have some users that love translating text errors into numeric error themselves. Any time a page doesn't load, it's a 404. So that's what they report. "I'm trying to connect to thisdomaindoesntexist.com and I'm getting a 404."