2. Inside JIRA Bug Processes
AND SOME JIRA BEST PRACTICES
Eric Dalgliesh
•
JIRA Team Lead
•
Atlassian
•
@ericdalgliesh

3. Overview
• JIRA’s triage process
• JIRA’s warranty bug process
• How we prioritize bugs
• JIRA’s QA processes
• JIRA’s workflow

4. Bugmaster: a single
developer responsible for
the management of bugs

5. A bug
• An error producing an unintended effect

6. A bug
• An error producing an unintended effect
• After JIRA is released

7. A bug
• An error producing an unintended effect
• After JIRA is released
• Generally excluding poor design

8. A bug
• An error producing an unintended effect
• After JIRA is released
• Generally excluding poor design
• Or anything else we want to call a bug

9. Not quite features; not
quite a bugs: fugs.

11. Triage
• Every day
• All new and updated bugs
• Focus on rapid response

15. Classification
• Components
• The area of the code base affected
• Labels
• The people who care about the issue
• Metadata

18. Public tracker
• Conversations
• Customer feedback
• Set expectations

21. “
”
This is affecting us too.

22. “
When will this be fixed?
”

23. “
If you fix this I will make all
”
your dreams come true.

24. Warranty bugs
• Faster to fix
• Raises new feature quality
• Developers responsible for quality
• Gives bugfix budget back to feature teams

27. Prioritization
• Keep our goals in
mind
Severe
customer
impact
Purchase and
Upgrade
Creeping
normalcy
High support
costs
Affecting
many
customers

28. Alternating theme work
• Retain some time for urgent work
• Work on themes to tackle hard problems
JIRA 5.2.x
JIRA 6.0.x
LDAP
High impact
&
urgent bugs
JIRA 6.1.x
Search

29. Board of Eric

30. Work allocation
• Match fix-rate to demand
• Fix in as few versions as possible
• Balance urgency and efficiency

31. JIRA Agile

32. Swimlanes

33. Cumulative flow

34. JIRA Workflow

35. Feature workflow - an aside

36. JIRA Workflow

37. Summary
• Triage daily
• Know why you’re fixing bugs
• Quality should belong to the developers
• Bug and story processes can differ
• Make it easy to give feedback
• Listen to that feedback

38. Thank you!
Eric Dalgliesh
•
JIRA Team Lead
•
Atlassian
•
@ericdalgliesh

39. Rate this Talk
Inside JIRA Bug Processes: JIRA Best Practices
Text code below to 22333
or visit http://bit.ly/197jucS
MEH = 2Z
NO T BA D = 30
P R ET T Y GO O D = 31
A WES O ME = 32
To join this session, send text 136888 to