Can Jira block "Done" until a checklist is finished? Not out of the box, as far as I can tell. There are three ways to get partway.
The first is the one everybody tries. You type [] in the description and get checkboxes. They look fine, and that is about all they do for you: as far as I can tell, the move to Done does not look at them.
The second is Jira Automation. A rule on "Work item created" can paste the same list into every story of a given type. Everybody gets the same list. Nobody is forced to finish it.
The third is the only native thing that says no: a workflow validator on the transition into Done. Jira's own is called Field Required Validator, you add it to the transition in the workflow editor, and it checks that a field has a value. So the usual trick is a "DoD confirmed" checkbox field that someone has to tick, which is still an honor system.
What I wanted was a list on the ticket where the required items themselves stop the move, and the error says which ones are open. Jira cannot do that alone, because it does not know what is inside your list. So I built Checklist Flow, and I should say plainly that I build it at Stanki Guild, so I am not neutral.
You mark items Required and add the validator to the transition. When someone drags the ticket to Done with required items open, Jira refuses and names the first three open ones, plus "and 4 more" if there are more. If no item is marked Required, every item counts. Tickets with no checklist are not blocked, unless you switch that on. And if the check itself fails for some reason, it blocks and asks you to try again. I did that on purpose, because a gate that opens when it breaks is not a gate. The validator works in the free edition; only its extra settings, like limiting it to one named checklist, are paid.
Three things changed in the 3.x versions that I actually care about. Items can have your own statuses, like "Blocked" or "Skipped", and each one is marked as counting as done or not, so "Skipped, with a reason" does not need a fake tick. That one is paid. The importer for Smart Checklist now also carries over its priorities and statuses, and a status only lands when your site already has one with that name, otherwise it stays in the item text, so run the dry run first. TitanApps says the free version of Smart Checklist reaches end of support on 15 December 2026, so if that is your list, the import is worth a look.
The last is the odd one. I let a Rovo agent read a checklist, do the items it can and report them with evidence, but its tick on a Required item does not count until a person confirms it. The gate still belongs to a human. That part is covered by tests, but I have only run the basic tool calls on a real site so far, not the whole confirmation path, and the agent tools are a paid feature.
It is not the only one. Smart Checklist and Checklists for Jira by HeroCoders do similar things.
What I do not know: how many of you want a hard block rather than a nudge. And the health report across a project reads 200 tickets per view and tells you when there are more, so on a big project it is a sample, not a count.
Do you gate Done on anything today, or do you trust people to remember?
