Drawing conclusions in bug reports

When I was become an EMT (Emergency Medical Technician), we were taught to observe and report without making a diagnosis, because we were not trained to do so. This concept also applies to bug reports. Over the years I’ve seen users/customers report bugs and attempt to say why the bug is happening. Unfortunately, many times the user is completely wrong. Without seeing the source code, knowing how things work, and/or not knowing a particular standard, it is nearly impossible to draw a conclusion as to why a problem is happening. I wish that bug reports would do what I was trained to do becoming an EMT; observe and report. Let the developers make the conclusions and fix the issue.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

*
To prove you're a person (not a spam script), type the answer to the math equation shown in the picture. Click on the picture to hear an audio file of the equation.
Click to hear an audio file of the anti-spam equation