Checklist automation that puts the quality bar on every work item

What is Jira checklist automation?

Checklist automation attaches a saved template to a Jira issue at a moment you choose — create, a status change, or a richer Jira Automation rule. The list is the same shape every time: Definition of Done on a Story, a QA testing checklist when work is Ready for test, a release checklist when status says Ready to release. People still tick the rows; the process just shows up without a scavenger hunt.

A template on the Advanced tab can add itself. A workflow validator can wait until the list is complete. A post function can reset the rows when you reopen. Jira Automation covers the cases that need labels, components, or a scheduled sweep. Pick the layer that matches who is allowed to change the process.

Why teams automate the list

A Definition of Done that lives in Confluence only helps the people who remember to open it. Auto-add puts the same steps on the work item, so progress is visible on the board and in JQL. New stories start with a scaffold. Testers get a pass when the status says they should. Reopening a bug resets the list so the next pass is honest.

The payoff is a quieter standup. Instead of “did we remember the QA list?”, the issue already has it. Protected templates keep the wording locked while people tick items and set statuses such as In Progress and Blocked. Per-template auto-add is built into Checklist for Jira and runs without Jira Automation credits.

When to apply it

Use auto-add on create for lists people need on day one — Definition of Done on Stories, a light intake list, a QA baseline on Bugs. Use auto-add on status change for a phase that starts later: Ready for test, Ready to release, In Review. Use a completion validator when Done should mean the bar is met. Use a reset when the same issue must run the process again.

Skip a rule when the list is optional or rare. Checklist for Jira still lets anyone who can edit checklists apply a template from Add → Add from template. Get the items right first, then turn on the rule on the Advanced tab.

Three layers that work together

Checklist for Jira gives you three places to encode the process. They stack; they do not replace each other.

• Per-template auto-add on the Advanced tab — add on issue creation, or add on status change, with a reapply behaviour if the list is already there.
• Workflow validators and post functions — require completion or a non-empty list, or reset / complete items on a transition.
• Jira Automation actions — apply template, complete all, reset all — when the condition is richer than create or a single status.

Recipes: trigger, action, result

Permissions, Protected templates, and reapply

Project administrators manage project templates. Jira administrators manage global templates. Anyone who can edit checklists on an issue can apply them from Add → Add from template. Protected templates lock the structure: people tick items and change status, but they cannot rewrite the steps — including from chat. Only one Protected checklist from a given template is allowed on an issue.

On status change, pick a reapply behaviour before you roll the rule out to the whole project. Do nothing keeps a one-time runbook (a second visit to Ready to release does not add another copy). Reset checklist is right when the same issue must run the pass again — a re-test after Reopened. Add the template again keeps a history of each visit. Archived templates skip auto-add and drop out of the picker; unarchive before you edit their rules. Details live in the product docs.

Save a template, then turn on the rule

1. Checklist for Jira adds a checklist panel on the issue view. Paste a starting list — Definition of Done, the QA testing checklist, or a release checklist — then save it as a project or global template in Checklist settings.
2. Mark the template Protected if the wording should stay locked while people tick items.
3. On the Advanced tab, add on issue creation (all types or specific types) or add on status change. For a global template, set those rules per project. These automations are built into Checklist for Jira and run without Jira Automation credits.
4. If Done should mean the bar is met, add an All Checklist Items Completed validator on that transition, scoped to this template so other lists on the issue can still be in progress. Checklist Not Empty is the lighter gate when you only need a list to exist.
5. A post function can reset or complete items on a transition. Use Jira Automation when the condition needs labels, components, or a scheduled sweep. Pair with the Rovo checklist agent when someone wants the right saved list in the moment.

Pair it with the rest of the delivery set

Start from the template hub — Definition of Done on create, the QA testing checklist on Ready for test, the release checklist on Ready to release. Keep each list on the parent when it is a quality bar; open a sub-task when the slice of work deserves its own issue — the checklists versus sub-tasks guide walks through that choice. Use the Rovo checklist agent for the unusual ticket; keep rules for the default.

FAQ