- Global configuration
- Template configuration
- Template scope
- Manage templates
- Supported fields
- Using templates
- Create issue from template
- Create issue structures
- Apply template to existing issue
- Recreate issue
- Use template custom field on issue create screen
- Default templates
- Direct link
- JQL searchers
- App Integrations
- Team-managed projects
- Jira Software
- Jira Service Management
- Advanced Roadmaps
- Issue Checklist for Jira
- Legacy automation action
- REST API
- Create issue and apply template with Jira REST API
Last updated Sep 20, 2021
This chapter provides a list of words used in documentation with explanations.
|Abbreviation for Issue Templates Cloud
|Template’s fields (Scope)
|These two terms are used interchangeably. Template’s fields (Scope) refers to fields from the template that will be copied.
|Project where your templates are stored.
|Project where issues from templates will be created. In the most basic scenario it’s the project selected in Create dialogs.
|Template that was explicitly selected in order to create issue or apply template from it. The primary template can be linked with secondary templates.
|Secondary templates (linked templates, subtasks, etc.)
|All templates that are used to create hierarchy but are not selected directly from Template Select. For example: linked templates, sub task templates, and basically all templates related to the primary template.
|Select rendered by the app.
|Template custom field
|Select custom field provided by the app and rendered by Jira.
|Create from template (CFT) dialog / view
|Dialog/view provided by the app, allows to select target project, issue type and the template, right before opening Create issue dialog.
|Create issue dialog
|Dialog provided by Jira to create issues.
When mentioned, it means it applies to both Create issue dialog and Create from template dialog.