2 / 3 · Book 18 · The Art of the Bug Report · drill: interview Q&A← prev⊞ allnext →Get the book →
1.10Exercises
Beginner
- Write a bug report for a real issue you have encountered recently, using the template from this chapter. Include all fields: title, priority, severity, component, environment, steps to reproduce, expected vs actual, additional context, and at least one attachment.
- Review five existing bug reports in your project. For each one, rate its quality on a scale of 1-5 and identify what is missing.
- Explain the difference between priority and severity in your own words. Give one example of a high-priority, low-severity bug from your product.
Intermediate
- Set up a daily triage process for your team. Write the agenda, assign a triage lead, and run it for one week. Document what worked and what did not.
- Create a Jira bug ticket template that enforces required fields (steps to reproduce, expected vs actual, environment, severity).
- Find five "Won't Fix" bugs in your backlog. For each one, verify that the decision is still correct given current product priorities.
Advanced
- Design a complete Jira workflow for bug tracking using the template in this chapter. Customize it for your team's specific needs (add or remove statuses, adjust conditions).
- Implement the workflow in a Jira project and train your team on it. Document the transition rules and share them as a team wiki page.
- Build an automated Slack notification that fires when a Critical bug is filed, including the bug title, priority, and a link to the ticket.