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): if more than three items land in testing at once, the column header warns you.
3In the transition matrix mark "In testing > Done" and put a role requirement on it: Tester only. 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. The two requirements work as OR.
5Write an auto-assignment rule on "In testing": assign to the reporter, or to the "Tester" person field on the task. The assignment replaces the current assignee, because what it means here is a handover.
6Under Board settings > Task templates create a "Bug report" template: issue type Bug, status Open, reproduction headings in the description, and the "Affects version" and "Severity" custom fields prefilled.
7Anyone picking "Bug report" from the template selector on the new task screen now starts from the same skeleton.

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, the move does not happen and a notice explains why. This used to be reverted silently with no explanation.