Inside JIRA Bug Processes: JIRA Best Practices

5,231 views
5,448 views

Published on

Published in: Technology, News & Politics
0 Comments
6 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,231
On SlideShare
0
From Embeds
0
Number of Embeds
2,523
Actions
Shares
0
Downloads
101
Comments
0
Likes
6
Embeds 0
No embeds

No notes for slide

Inside JIRA Bug Processes: JIRA Best Practices

  1. 1. Inside JIRA Bug Processes AND SOME JIRA BEST PRACTICES Eric Dalgliesh • JIRA Team Lead • Atlassian • @ericdalgliesh
  2. 2. Overview • JIRA’s triage process • JIRA’s warranty bug process • How we prioritize bugs • JIRA’s QA processes • JIRA’s workflow
  3. 3. Bugmaster: a single developer responsible for the management of bugs
  4. 4. A bug • An error producing an unintended effect
  5. 5. A bug • An error producing an unintended effect • After JIRA is released
  6. 6. A bug • An error producing an unintended effect • After JIRA is released • Generally excluding poor design
  7. 7. 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
  8. 8. Not quite features; not quite a bugs: fugs.
  9. 9. Triage • Every day • All new and updated bugs • Focus on rapid response
  10. 10. Classification • Components • The area of the code base affected • Labels • The people who care about the issue • Metadata
  11. 11. Public tracker • Conversations • Customer feedback • Set expectations
  12. 12. “ ” This is affecting us too.
  13. 13. “ When will this be fixed? ”
  14. 14. “ If you fix this I will make all ” your dreams come true.
  15. 15. Warranty bugs • Faster to fix • Raises new feature quality • Developers responsible for quality • Gives bugfix budget back to feature teams
  16. 16. Prioritization • Keep our goals in mind Severe customer impact Purchase and Upgrade Creeping normalcy High support costs Affecting many customers
  17. 17. 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
  18. 18. Board of Eric
  19. 19. Work allocation • Match fix-rate to demand • Fix in as few versions as possible • Balance urgency and efficiency
  20. 20. JIRA Agile
  21. 21. Swimlanes
  22. 22. Cumulative flow
  23. 23. JIRA Workflow
  24. 24. Feature workflow - an aside
  25. 25. JIRA Workflow
  26. 26. 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
  27. 27. Thank you! Eric Dalgliesh • JIRA Team Lead • Atlassian • @ericdalgliesh
  28. 28. 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

×