How to Report Bugs the Smart Way [closed]

Question

I want to write (or find) a guide to effective bug reporting in a style similar to ESR's How To Ask Questions The Smart Way

What are your top tips for effective bug reports?

Answer 1

Recommend this article: How to Report Bugs Effectively

Answer 2

• Procedure used to re-create the bug including what was being done, what area of the application was being used and what event was happening at the time.
• Statement of reproduceability (reliably, not) - helps the developer know how hard it should be to reproduce so they don't give up to quickly
• Screen shots or documentation of error message / stack trace produced
• Criticality/Priority of the bug (can it be avoid, avoidance steps, is it catastropic, does it have a business impact, what's the business risk, etc)
• Environment - which environment was the bug found in. Remote, local, etc.

Too often, our QA people think they can just put in a ticket saying, here's my exception without any backup documentation. Its near impossible to reproduce let alone fix the issue without more information.