- Get started
- About
- Glossary
- First steps
- Migration to Cloud
- Integrations points
- Create issue from template
- Recreate issue
- Apply template
- Apply template post function
- Legacy automation action
- Template custom field on issue create screen
- Apply template via issue property
- Configuration
- Repository
- Template's configuration
- Using templates
- Copy Epic
- Copy links and linked issues
- Copy Subtasks
- Copy Initiatives
- Default templates
- Using Variables
- Static variables
- Dynamic variables
- Smart defaults
- Basics
- Smart issues
- Smart users
- Smart dates
- Smart project
- How to use smart defaults
- Security
- Security statement
- App permissions
Last updated Sep 20, 2021
Tables below show which fields and elements you can copy with Issue Templates.
| System fields | Special handling and exceptions |
|---|---|
| Attachment | Copied |
| Fix versions, Affects versions | If an element is missing in a target project, the app will create it on your behalf. Initiator requires permissions to create it. |
| Components | If an element is missing in a target project, the app will create it on your behalf. Initiator requires permissions to create it. |
| Summary, Description, Environment | Copied |
| Time tracking | Copied |
| Due date | Copied |
| Priority | Copied |
| Labels | Copied |
| Assignee, Reporter | Copied |
| Jira Software | |
| Sprint | Active and future sprints are copied |
| Epic link | Epic link serves a purpose to link parent ↔︎ child relations and it is set by Issue Templates when child issues of the epic template are created. It is always rewritten to point to a new parent and match new hierarchy. When you apply a template to a story, and your template points to an epic that is not a template, then if an Epic Link is in a scope it will be copied exactly as it is. In this scenario, if an Epic Link points to a template, it won’t be copied. |
| Jira Software Premium | |
| Team | Copied |
| Jira Service Management | |
| Organizations | Copied |
| Request Participants | Create from template action restrictions - Autocomplete cant’t be supported, Jira doesn’t display the field despite presence on the Create screen. The app will copy the value in the background if it isn’t added to the Create screen. |
| Customer Request Type* | In order to copy a Request type between service desks, in both projects, a request type with the exact same name and issue type must exist. A request type must be publicly available (assigned to any portal group), hidden request types can’t be copied. Create from template* action restrictions: Autocomplete cant’t be supported, When the Create issue dialog is opened by apps, Jira doesn’t display the field despite presence on Create screen. The app will copy the value in the background if it isn’t added to the Create screen. |
| Custom fields | |
| External Asset Platform | Link assets that have been made available via marketplace apps on external inventory platforms outside Jira. |
| Checkboxes | Copied |
| Date Picker | Copied |
| Date Time Picker | Copied |
| Labels | Copied |
| Number Field | Copied |
| Paragraph | Copied |
| Radio Buttons | Copied |
| Select List (cascading) | Copied |
| Select List (single or multiple) | Copied |
| Short text | Copied |
| URL Field | Copied |
| User Picker (single or multiple) | Copied |
| Group Picker (single or multiple) | Copied |
| Project Picker | Copied |
| Version Picker (single or multiple) | Copied |
Fields that can’t be copied
Not supported fields:
- Status
Custom fields that are set by Jira and cannot be edited by Issue Templates:
- Date of First Response
- Date of First Response
- Domain of Assignee
- Domain of Reporter
- Global Rank
- Last commented by a User Flag
- Last public comment date
- Number of attachments
- Number of comments
- Participants of an issue
- Username of last updater or commenter
Jira Service Management fields that can only be set by JSM:
- Approvals
- Satisfaction
- Satisfaction date
- Request language
