Timeline for Getting users to write decent and useful bug reports
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 18, 2012 at 22:24 | comment | added | mattnz | My point is that if "it crashed" is what happens from the perspective of the user. When I take my car to a mechanic, he does not expect me to give him an expertly detailed diagnostic report of what is wrong - he asks me questions to help him use his expertise to diagnose the problem. For instance one visit my problem was "It stalls when its cold, but is ok when its hot", a few well considered questions (with yes no answers)later he was fairly sure (and turned out to be correct) it was a faulty thermometer. Our job is to ask the questions, framed to give yes not answers. | |
| May 18, 2012 at 11:40 | comment | added | Michael Kohne | I don't think the OP is saying they don't want to deal with users. I think the OP is saying that they can't really fix anything based on the bug report 'it crashed'. The OP wants a way to get the most of out of the users who are complaining, so that the OP can actually FIX the problem. | |
| May 18, 2012 at 10:50 | history | edited | Scott C Wilson | CC BY-SA 3.0 |
typo corrections
|
| May 18, 2012 at 8:24 | history | edited | gnat | CC BY-SA 3.0 |
minor typo correction
|
| May 18, 2012 at 7:42 | history | answered | mattnz | CC BY-SA 3.0 |