Child work items and sub-tasks
On this page
A template can list work items to create under the one it makes: for an epic, its stories and tasks, and sub-tasks under each. They are created one at a time, in the order the template lists them: each child, then its sub-tasks, then the next child.
Setting them up
In the template editor, under Child work items, choose Add child work item, pick its work type and write its summary. Add sub-task adds a sub-task under it. Up and Down change the order, and Details opens its description, checklist, labels and priority. The editor shows how many work items the template creates in all.
What fits depends on the work type the template is for, as in Jira itself. Under an epic, standard work types (story, task, bug) go; under a standard work type, only sub-tasks; and nothing goes under a sub-task. So a tree is at most two levels below the work item it starts from.
A summary or description can use three placeholders, filled in when the work item is created:
{{parent.key}}: the key of the work item it goes under, for exampleCP-5.{{parent.summary}}: that work item's summary.{{today}}: the date, as2026-10-21.
For a child, the parent is the work item the template made or was added to. For a sub-task, it is the child above it.
From the Templates page
A template with child work items says creates N work items under it on its card, and Show the work items it creates lists them. Create opens Jira's Create dialog for the top work item as usual. Once it is created, the page adds the child work items under it and shows how far it has got, then the keys of everything created. Keep the page open until it says so. If it is closed early, what was created is kept, and the rest can be added from the work item's ••• menu.
On a work item that already exists
In a work item's ••• menu, Add work items from template lists the project's templates that have child work items. Pick one to see what will be created, in order, with the placeholders filled, and any work type that does not fit this work item. Create adds them under it. The work item itself is not changed, and nothing already under it is touched. A run that stopped part-way is listed there as Unfinished, with Resume.
From a Jira Automation rule
The app adds an action to Jira Automation: Add work items from template, under Other apps when you add an action to a rule. It does what the ••• action does, for the rule's work item.
Not in Atlassian Government Cloud: Jira Automation there does not offer the app's actions.
- The first time, Jira asks you to Connect the rule to the app. The action then runs as that connection's user, with their Jira permissions.
-
In the action, choose the template and the work item, usually
{{issue.key}}: the rule's own work item. For example: when an epic is created, add the release template's stories and sub-tasks under it. - One rule run creates what it can in about 20 seconds; small trees finish in one go. A larger one is left as Unfinished on the work item, to resume from its ••• menu.
- If Jira refuses an item, the action fails with Jira's message, and the rule's audit log shows it. What was created is kept.
-
The action passes
created,total,statusandrunIdon to later steps of the rule.
A second action, Create work item from template, creates the template’s own work item too, so a rule can start work without an existing work item: for example, a scheduled rule that creates the weekly operations checklist every Monday.
-
Choose the template, the project (usually
{{project.key}}: the rule’s project) and, when the template fits more than one work type there, the work type by name. The template must be used in that project. -
Summary is added after the template’s own summary,
and smart values work there, for example
{{now.jiraDate}}: a template whose summary is “Release ” then creates “Release 2026-11-02”. - The work item gets what a pick on the Templates page puts in Jira’s Create dialog: summary, description with its checklist, labels, priority, assignee, due date, components and custom fields. “The person using the template” is the rule’s user. Then its child work items follow, in order, as above.
- Work types are checked before anything is created. A field that is not on the work type’s create screen is left out, and the rule’s audit log names it.
-
It passes
key(the new work item), andcreated,total,statusandrunIdfor its children, on to later steps.
When Jira refuses an item
Before anything is created, every work type is checked against the project. Even so, Jira can refuse an item, for example when its work type needs a field the template does not fill. The run then stops at that item and shows Jira's message. Everything already created is kept. You can:
- Resume, after fixing the cause, such as a permission or a required field. Nothing is created twice, even if the page was closed while an item was being created.
- Skip this item, when the template itself is the cause. That item and the sub-tasks under it are left out, the rest is created, and the result names what was skipped.
A run keeps the template as it was when it started, so editing the template does not change a run already under way. If a work type's create screen lacks labels, priority or description, the item is created without that field, and the result says so.
Child work items are created with the permissions of the person using the template, and they need Jira's Create issues permission in the project.