If you’re new to bug tracking, issue management or web development in general, you might wonder what a bug report is. In this slideshare presentation I try to answer this question from different viewpoints. And trust me, it’s not going to be boring. So, let me answer the question “What is a bug report?” for you. In order to answer this question, we need to understand the following concept of bugs, bug reports and bug reporting software.

1. @tompeham I @usersnap
BUG REPORT?
WHAT IS A

2. THIS IS ME!
@TOMPEHAM I @USERSNAP

3. @TOMPEHAM I @USERSNAP
Say hi!
THIS IS ME!

4. You can access the entire article here.

5. WE ALWAYS TALK ABOUT
BUG REPORTS

6. Not even Google &  are interested in bug
reports
Ironically, Google doesn’t answer the question of
a bug report either. If you search for bug report
on google.com, the first entry is a link to Apple’s
bug reporter.

7. That’s pretty hilarious, because Apple is often critiqued
for it’s bad bug reporting tool.

8. So, what is a bug report?

9. So, what is a bug report?
In order to answer this question, we need to understand
the following concept of bugs, bug reports and bug
reporting software.

10. So, what is a bug report?
bug bug report bug report tool

11. What is a bug?
This is a bug

12. What is a bug?
“A software bug is an error, flaw, failure, or fault in a
computer program or system that causes it to produce an
incorrect or unexpected result or to behave in unintended
ways.”

13. What is a bug?
A software bug is an error, flaw, failure, or fault that
produces an incorrect or unexpected result.

14. The origin of a “bug”
You might wonder, why a bug is called a bug? It’s a great
question, because the term bug, describing an software
error or failure goes way back to 1945.
1945

15. The origin of a “bug”
In late 1945, at the University of Harvard, a technical team
found something unusual between points in Relay70. The
found a real dead bug (the animal) which caused an error.

16. The origin of a “bug”

17. What is a bug report?
This is a bug report

18. What is a bug report?
A bug report “should explain how exactly the product is
broken.”
A bug report should follow this simple formula:
“This is what we have, this is what we should have instead,
so fix it.”

19. What is a bug report?
How a bug report
should NOT looks like.

20. Good vs. bad bug reports
A good bug report contains the information needed to reproduce and fix problems
A bad bug report does not contain the information needed to reproduce and fix
problems
A good bug report is an efficient form of communication for both bug reporter
and bug receiver
A bad bug report is a lengthy, inefficient form of communication for everyone
involved
A good bug report is resolved as fast as possible
A bad bug report never gets resolved
A good bug report is sent to the person in charge
A bad bug report isn’t filed at all

21. Good vs. bad bug reports
A good bug report is on point
A bad bug report contains no specific information
A good bug report is filed in the defined way
A bad bug report is filed in any medium available, but not in
the defined way (little hint: Twitter isn’t a good way to file a
bug report ;-))
A good bug report establishes a common ground of
collaboration
A bad bug report doesn’t enable collaboration

22. What is a bug reporting tool?
This is a bug
reporting tool

23. What is a bug reporting tool?
A bug reporting system is an application “that keeps track
of reported software bugs”.
Therefore, a bug reporting software allows you to report,
document, store, manage, assign, close & archive bug
reports.

24. OVER TO
YOU
There are a lot of do’s and don’ts when it comes to
the bug reporting workflow, from bugs, to no bugs.

25. @tompeham I @usersnap
OUR BLOG AT
ALSO CHECK OUT
USERSNAP.COM/BLOG