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 *

This site uses Akismet to reduce spam. Learn how your comment data is processed.