Checklist templates

A template prefills ToDo List fields on issues as they are created. Templates are managed on the admin page, Templates tab, by Jira administrators.

Templates and the default items of a field context are two different things:

  Default items (field context) Template (admin page)
Set up in The field context configuration Admin page → Templates
Applies to Issues the context covers Projects and issue types chosen in the template
When When someone opens the editor on an empty field; nothing is stored until they save When the issue is created; the checklist is stored at once
Visible to JQL, panel and exports before anyone edits No Yes

Creating a template

New template opens the form:

Setting Default Notes
Name — Required, up to 255 characters.
Apply this template to new issues On Turn off to keep a template without using it.
Projects Any project Leave empty to apply in every project.
Issue types Any issue type Leave empty to apply to every issue type.
Checklist items — Each item has a text, a status, Mandatory and Header; reorder with Move up / Move down. Up to 100 items.

Save checks the form first. If something is wrong, the form stays open and “Fix the following before saving” at the top of the form lists every problem (for example “Template name must not be empty.”, “Template must contain at least one item.”); an empty or too long name also marks the Name field red, with the problem under it. When the form is taller than the dialog, the form scrolls between the title and the Cancel / Save buttons, which stay in place.

The list shows each template’s name, its items, where it applies (Applies to) and its status (Enabled / Disabled), with Edit and Delete. All templates are on one page: the list has no page switcher and no empty strip below it. Deleting a template does not touch the checklists it already created. A site can have up to 100 templates.


How a template is applied

  • When an issue is created, the app finds the enabled templates whose projects and issue types match the issue (an empty rule matches anything).
  • If several match, the most specific wins: a template with both projects and issue types beats one with only one of them, which beats one with neither. Between equally specific templates, the one whose name comes first alphabetically wins.
  • The template is written into every empty ToDo List field of the new issue. A field that already has items — for example, filled in on the create screen — is left as it is.
  • Templates are applied only on creation. Editing a template does not change existing issues.
  • While the license is not active, templates are not applied, and templates cannot be saved or deleted: the admin page shows “This app requires an active license. Check the app license in Manage apps.” Existing templates stay and can still be viewed.