The validator blocks a transition while the ToDo List checklist still has unresolved mandatory items.
Adding it
In the workflow editor, add the validator ToDo List: mandatory items resolved to a transition and fill in the form:
| Setting | Default | Effect |
|---|---|---|
| Checklist field | All ToDo List fields | Pick a field to check just that checklist, or leave it on all fields. |
| Message shown when the transition is blocked | Empty | Optional, up to 500 characters (longer text is cut). Shown to whoever tries the transition. |
In the new workflow editor, the rule is stored on the transition by Jira’s Add button. The form’s Save keeps what you entered and says “Saved in the form. Press Add in the workflow editor to put the rule on the transition.” — the rule is not on the transition until you press Add. In the old workflow editor, Save stores the rule itself.
The Checklist field list is read from Jira each time the form opens, so a ToDo List field created or renamed a moment ago is offered right away, under its current name.
If the site has no ToDo List field yet, the form says “No ToDo List field is set up on this site yet. The validator will let every transition through until an admin adds one.” A field that was deleted later is shown as “Field no longer on this site (…)”.
What it checks
- The transition is blocked when a checked field has at least one mandatory item that is not resolved (its status does not count as done in the field context).
- Without a custom message, the user sees, for one field: “<field name>” still has N unresolved mandatory item(s).; for several fields: Unresolved mandatory checklist items in “<field>” (N), “<field>” (N).
- An issue whose checklist is empty, has no mandatory items, or does not carry the checked field passes.
- If the app cannot read the issue from Jira at that moment, the transition is let through rather than blocked.

