Bug reporting should never be a chore. QA is the worst job in the IT industry. You're already getting people to do it for free, and only after you've already inconvenienced them by giving them broken software, possibly screwing over very real work they need to get done. Making them spend 30 minutes figuring out your crazy byzantine process just to send you a file that crashes the app when they try to open it is insulting.
If they leave out some info, you respond and ask for more. If they don't respond within a week, or the email address they provided bounces, then the system automatically closes out the bug as NO-RESPONSE (and re-opens it if the user responds at a later date). Then you also avoid the Bugzilla problem of having a hobajillion backlogged NEEDINO bugs that build up over the months or years.
The fact that "most projects" have some Bugzilla-based middle ground doesn't mean that It Works Perfectly(tm). It just means they've settled for less because they didn't bother to really think about their software's QA process or the value of their users' time.
Posted Sep 2, 2010 17:57 UTC (Thu) by zlynx (subscriber, #2285)
[Link]
No, working as a programmer trying to fix "bugs" filed as "It does not wrk fix it kthx." is the worst job.
I want debug symbols. I want a stack trace. I want the *exact* version of the software, what it was compiled with, what libraries it was linked to, what file it was working on. I want verbose debug logs.
PostgreSQL 9.0 Release Candidate 1
Posted Sep 3, 2010 10:11 UTC (Fri) by mpr22 (subscriber, #60784)
[Link]
Write up a description telling Joe Luser how to get those things (starter for ten: Joe Luser doesn't know how to change his core dump size ulimit away from the distribution default of zero). Configure the bug tracking system to send it automatically to the submitter of any bug you close with an "no information" resolution code. Close content-free bug reports with the "no information" resolution code.
Alternatively, don't write programs for normal people to use.