Check the definitions of the most important terms
| Term | Definition |
|---|---|
| Template | Template is a Jira issue that can be applied to other issues, or create new issues in different target projects. When users select it on a screen, it autofills fields with predefined values. |
| Target issue | Target issue means any issue to which a template is applied. |
| Template repository project | Template repository project is a Jira Software project containing all the templates. It gets created right after installing the app. It should be separated from target projects and contain only template issues. By default it is called Templates (TEMP). |
| Target project | We call any Jira project where templates are applied a target project. |
| Template field | The Template field is a custom field provided by the Issue Templates app. It’s a single-select list allowing users to choose a template on a screen. |
| Template navigator | Template navigator is a separate page under the repository project. It contains all the templates and allows you to browse, filter, and configure them with many useful settings. |
| Template details | Template details are settings that apply to a particular template. It consists of six tabs: General, Fields, Availability, Context, Relations, and User variables. It is available in the Template navigator, as well as in any particular template issue. |
| Global configuration | Global configuration is a page dedicated to Jira admins. It contains settings that apply to all the templates across Jira. |
| Set of fields | Set of fields defines what Jira fields and custom fields should be affected by the template in the target issue. You can modify it and create new sets for a single template in the Fields tab. Jira admins can define global settings on the Set of fields page. It is sometimes called the template’s scope. |
| Availability | In the Availability tab you can decide where a template should be visible for users and under what conditions. Advanced settings allow Jira admins to define Default availability settings for all the templates. |
| Variables | Variables are placeholders that get automatically filled in in the target issue. There are two types of variables: System variables and User variables. |
| Autofill | Autofill is the most basic features and works without any post functions. It allows for filling in fields in the target issue with values defined in the template’s Set of fields. The fields are filled in after selecting a template on a screen. |
| Create Structure post function | The Create Structure post function is necessary for copying additional values (for example, attachments, issue links, comments, and more) from a template to the target issue. It also allows for creating subtasks and entire epics with stories from a single template. It makes it possible to use templates on different workflow transitions. |
