Learn

QA process guides

Process is where most bug reports die: filed without the detail to reproduce, triaged in a meeting nobody wants, or parked in a backlog until the context is gone. These guides are written for small teams that do QA alongside building, not for a dedicated QA department.

Each one is a working method with the steps written out: how to run triage so it ends in decisions, how to plan a bug bash whose output can be fixed, and which Jira fields earn their place in a bug report.

Start here: Bug Triage: How to Run It Without It Becoming a Status Meeting; How to Run a Bug Bash That Produces Fixable Bugs; then Jira Bug Report: Template, Example, Fields and Workflow.

How to Run a Bug Bash That Produces Fixable Bugs A bug bash is a timeboxed session where a whole team hunts bugs in one area at once. How to scope, run and triage one — and what makes the reports usable.
Jira Bug Report: Template, Example, Fields and Workflow A Jira bug report template to copy, a filled example, how Jira models a bug, and the Resolution field that quietly decides what counts as fixed.
Bug Triage: How to Run It Without It Becoming a Status Meeting Bug triage decides what gets fixed and what does not. How to run it, how severity and priority differ, and why most triage meetings quietly stop working.