A bug flow that cannot close unverified

A flow where only the tester can close work, and recurring bugs open from a template.

The goal is a process that defends itself: a developer can move work to "ready to test" but cannot declare it done, work landing in testing reaches the right person, and every bug record carries the same information.

Steps

1Under Board Settings > Workflow set up the statuses: Open, In development, Ready to test, In testing, Done. Pick the right category for each - the "Done" category feeds burndown and velocity, and it is the category that counts, not the name.
2Put a WIP limit on "In testing" (say 3): while the column is full, a fourth item cannot be moved there or created there until one leaves.
3Under Board Settings > Transitions, define every allowed transition with "Add transition" and turn on "Only allow the transitions defined below"; while it is off, undefined transitions are free and a developer could jump from "Ready to test" straight to "Done". On "In testing > Done", pick Tester under "Required roles". A developer moves work to "Ready to test" and can take it no further.
4If the gate belongs to one or two specific people, use a person requirement instead of a role: you do not have to define a role to name two people. There is a third way: pick a person field such as "Tester" on the task, and whoever is in it at the time can make the move. Any one requirement is enough.
5Write an auto-assignment rule on "In testing": assign to the reporter, to the "Tester" person field on the task, or to a specific person. The assignment replaces the current assignee, because what it means here is a handover.
6Under Board Settings > Templates create a "Bug report" template: issue type Bug, status Open, reproduction headings in the description, and the "Severity" custom field prefilled. Affects Version is a system field and a template cannot fill it; if it must not stay empty, mark it required under Task Screen.
7Anyone picking "Bug report" from the template selector on the new task screen now starts from the same skeleton.
8If every bug record must carry the same information, turn on "Description must match a task template" under Board Settings > General: choosing a template becomes mandatory on a new task and the template’s required sections cannot be left empty.

A transition rule is a lock, not a hiding place. If someone without the right drags the card or presses the forward arrow in the task panel or writes a /status quick action in the description, the move does not happen and a notice explains why. The message also names the role the move requires.