STM for Jira Cloud and Data Center

Templates can be used to create commonly used sets of issues, saving you from manually recreating the same issues repeatedly. With templates, you can automatically or manually generate these issues, ensuring a perfect copy each time.

Additionally, update templates allow you to modify values in existing templates. You can update field values, add comments, and/or add watchers.

Templates can be applied manually or automatically and can be specified for a single project or globally across multiple projects.

Templates can create issues in more that one project by specifying the project key for the issue (if different than current project).

See the Executors feature for more information on automatically creating templates.

When defining values for the summary or description, you can reference the fields from the parent issue. 

You can Also refer to the parents assignee or reporter in the issues assignee and reporter fields.

See Create Issue

You can copy field values from the parent issue to the issues being created. These values are only copied to the new issue if there is no value specified for the issue.

See the Copy From Parent section

Specify additional templates to be created for each new issue. You can specify more than one template.

For example, suppose we have a primary template that creates two issues, A and B, and specifies two cascading templates, T1 and T2. Issues A and B would be created first. Then, templates T1 and T2 would be applied to both issues A and B, in sequence.

See Cascading Templates

This feature allows you to repeat the current template multiple times based on a selected field (just components or versions). For instance, if you have two components, the template will be created twice, once for each component.

Sett Repeat Template

Executors are STMs method for automatically performing the following actions:

1. Creating issues (sub-tasks, linked issues, Epic issues) for a newly created parent issue
2. Creating issues (sub-tasks, linked issues, Epic issues) when a parent transitions from one status to another
3. Creating issues (sub-tasks, linked issues, Epic issues) when selected fields in a parent issue change value
4. Unconnected issues (those without a parent) can also be created when another issue is created, transitions between statuses, or has field values changed.
5. Updating an issue immediately after its creation
6. Updating an issue following a status transition
7. Updating an issue when selected field values change
8. Transitioning all child issues (sub-tasks or linked issues) to a new status when the parent issue’s status changes
9. Transitioning the parent issue of sub-tasks or linked issues to a new status when the first or last child issue changes status

Executors have conditions about when they should run. A single Executor can be created for one project or for multiple projects.

See the Project Executors for more details

Within the issue page there are options, in the triple dot menu, to create an template for sub-tasks, linked issues, Epic issues or unconnected issues (those without a parent).

The manual creation allows you to

1. Specify an existing template
2. Specify a modified version of an existing template (changes are not saved)
3. Specify a new template to create (changes are not saved)

There is a STM Bulk Create/Update page that allows you specify a JQL query where a template will be applied to all of the issues returned from the query. This can be a create or update template.

Create templates can create sub-tasks, linked issues or Epic issues. An existing template can be used in its existing state or modified. You can also specify a new template to use (not saved)