Limits, and where templates do not apply
Only in Jira's Create dialog. A template is filled in when it is picked on the Templates page, which opens Jira's Create dialog. The line naming a default appears only in that dialog. Issues created any other way get neither: inline on a board, backlog or list, by email, through the REST API or Automation rules, by import or cloning, from the mobile apps, or from a service project's portal.
Atlassian lists these ways into the Create dialog: the
Create button, the c keyboard shortcut,
and an app's own Create button, like the gallery's. Add a
child issue and Create subtask open it only
when the issue type requires a summary and at least one other field.
- Which fields. A template fills Summary, Description with the checklist, Labels and Priority, and can set the assignee, a due date, components and custom fields (how). Not versions, user-picker fields or a named assignee.
- Sub-tasks come from a parent. Sub-task work types are never offered as the top work item in the gallery. A template creates sub-tasks as part of its child work items.
- Project types. Atlassian documents the Create dialog support this app uses for company-managed and team-managed software and business projects. Service projects and Jira Product Discovery are not on that list, and we have not tested them.
- A moment after opening. Jira runs the app once the dialog has loaded, so the line under Summary can take a few seconds to appear.
- Gallery picks. The gallery marks its pick in that browser tab, so its Create dialog gets no line. If the browser blocks site storage for apps, the mark is missing: a picked template that is also a default can then get a line naming the chosen issue type's default. For up to two hours after a gallery dialog that Jira did not report closing, Create dialogs in that tab get no line.
- Other apps. Up to five apps can change the Create dialog at once. This app sets no field values there. It only adds its line to the Summary field's help text, after any help text already there.
- Issue types are matched by name. If you rename an issue type, edit the templates that name it. The health check lists them.
- The checklist is Jira's own action items in the description, not a separate checklist field.
- Numbers. 200 templates per site. 50 projects and 30 issue types per template. Up to 30 child work items per template, 20 sub-tasks under each, and 100 work items in all. One default per issue type per project. Project lists and the Apps gallery show up to 500 projects. The priority list shows up to 50 priorities. A check from the page covers up to 60 projects, the daily check up to 1,000.
- One project's defaults together must fit in Jira's limit of 50,000 characters for Create dialog settings. If they do not, the template is still saved, but that project's Create dialog is not updated and keeps its previous settings. The page lists the project with The default templates for this project are too long for Jira to carry.