Preventing moving work items to done while a checklist is not completed
To block moving a work item to Done (or Closed, or another state) until a checklist is finished, use Azure DevOps work item rules together with a Complete field mapped by the extension (Premium).
Why rules need mapped fields
Work item rules run against fields on the work item. The checklist UI alone is not a first-class rule target in Azure DevOps process rules. The extension syncs completion to a Single line text field (Yes when complete, empty when not) when you configure a Complete field mapping (Premium).
Until Progress and Complete are mapped and present on the form, the extension surfaces guidance that rules cannot enforce checklist completion until you finish field setup in Working with templates.
The template editor is where the Complete field mapping is configured before Azure DevOps rules can use it:

Typical pattern
- Create or pick a Single line text field (for example
Checklist completeor your process equivalent). - Map it as the Complete field for the template in Checklist Templates.
- In Organization settings → Process (or inherited process), add a rule on the work item type:
- When state changes to
Closed/Done(or your terminal state), - And the Complete field is empty (or not equal to
Yes, depending on how your process expresses the condition), - Then prevent the transition (or show validation), depending on what Azure DevOps Server/Services supports for your process version.
- When state changes to
Exact rule authoring differs between Inherited and Hosted XML processes. Refer to Microsoft’s work item rules documentation for your version.

Queries and pipelines
Because completion is a normal field, you can also use queries or quality gates in pipelines that read the same field. See Customising cards with checklist progress & completion.
Related topics
- Enabling style rules — visual emphasis on the board for incomplete checklists.