# Issue Templates: child work items, custom fields, Jira Automation and moving between sites

21 October 2026 · Issue Templates 2.6.0 to 2.13.0 · Issue Templates & Create Defaults for Jira

Between 20 and 21 October 2026, Issue Templates went from 2.6.0 to 2.13.0. Together, these versions turn a template into a whole piece of work: the work item, its children, their fields, and rules that create them.

## In short

- Templates create child work items and sub-tasks under the work item, in order, with a preview.
- They set the assignee, a due date, components and custom fields, on children too.
- Two Jira Automation actions create from a template.
- Templates move between sites by export and import, and the Create dialog no longer fills itself in.

## 2.6.0: the Create dialog no longer fills itself in

Jira can re-run an app on a form that already holds someone’s text and report it as empty, and an automatic fill could then replace that text. So the Create dialog no longer writes a default template into the form. Until Jira tells apps which form they are on, the Create dialog names the default template under Summary instead. Picking a template on a project’s Templates page still opens Jira’s own Create dialog with it filled in.

## 2.7.0 and 2.8.0: child work items and sub-tasks

A template can create child work items and sub-tasks under the work item it makes, in the order you set, with `{{parent.key}}`, `{{parent.summary}}` and `{{today}}` filled in. **Add work items from template**, in a work item’s ••• menu, adds a template’s work items under an existing one after a preview; the work item itself is not changed.

Before anything is created, every work type is checked against the project. If Jira refuses an item, what was created is kept: resume (nothing is created twice) or skip that item. Version 2.8.0 also adds three example templates in one step, built from the project’s own work types.

## 2.9.0 and 2.10.0: assignee, due date, components and custom fields

Templates set the assignee (the person using the template, or unassigned), a due date a number of days after creation, and components, on the template and on each child work item. No account is stored: “the person using the template” is read at that moment.

They also set custom fields: short text, paragraph, number, date, dropdowns and radio buttons, multi-select and checkboxes, labels and URL. Options are kept by name and matched in each project. A value Jira refuses for a child work item is left out, and the result names the field.

## 2.11.0 and 2.13.0: Jira Automation

Two new Jira Automation actions:

  - **Add work items from template** adds a template’s child work items and sub-tasks under the rule’s work item, for example when an epic is created. It runs as the rule’s connected user, with their permissions, and passes created, total and status on to later steps.

  - **Create work item from template** creates the template’s own work item, with all its fields, and then its children in order. For example, a scheduled rule that creates the weekly operations checklist every Monday.

## 2.12.0: moving templates between sites

Jira admins export every template as text and import it on another site, or keep it as a backup. Projects go by key, priorities and custom fields by name. A check shows what fits before anything is saved, and existing templates are never overwritten. The daily check now also reports a custom field taken off a create screen, and a component a project no longer has.

## Read more

- [Child work items](https://eriksenlabs.com/docs/issue-templates/child-work-items)
- [Assignee, due date and components](https://eriksenlabs.com/docs/issue-templates/fields)
- [Moving templates to another site](https://eriksenlabs.com/docs/issue-templates/move)
- [The health check](https://eriksenlabs.com/docs/issue-templates/health-check)

Source: the release notes for each version on the [Issue Templates & Create Defaults for Jira listing](https://marketplace.atlassian.com/apps/2217571549/issue-templates-create-defaults-for-jira) on the Atlassian Marketplace.

Published at https://eriksenlabs.com/insights/news/issue-templates-child-work-items-fields-automation
