The table below shows which fields and elements you can copy with Issue Templates for Jira Cloud:
| System field | Copied / special handling or exceptions |
|---|---|
| Assignee | |
| Attachment | Copied after an issue is created. |
| Checkboxes | |
| Components | If an element is missing in a target project, the app creates it on your behalf. The initiator requires permissions to create it. |
| Custom fields | |
| Customer Request Type* | 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 can’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 copies the value in the background if it isn’t added to the Create screen. |
| Date Picker | |
| Date Time Picker | |
| Due date | |
| External Asset Platform | Link assets that are available via marketplace apps on external inventory platforms outside Jira. |
| First comment | Once added to a scope it enables copying the first comment from a table. |
| Fix versions, Affects versions | If an element is missing in a target project, the app creates it on your behalf. The initiator requires permissions to create it. |
| Group Picker (single or multiple) | |
| Labels | |
| Number Field | |
| Organizations | |
| Paragraph | |
| Parent | Copied after an issue is created. Parent field serves a purpose to link parent ↔︎ child relations and it’s set by Issue Templates when child issues are created. It’s always rewritten to point to a new parent to match the new hierarchy. When you apply a template to a story, and your template points to an epic that isn’t a template, then if the Parent field is in a scope it is copied exactly as it is. In this scenario, if the parent points to a template, it isn’t be copied. |
| Priority | |
| Project Picker | |
| Radio Buttons | |
| Reporter | |
| 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 copies the value in the background if it isn’t added to the Create screen. |
| Select List (cascading) | |
| Select List (single or multiple) | |
| Short text | |
| Sprint | Active and future sprints are copied. |
| Summary, Description, Environment | |
| Target start (Advanced Roadmaps) | |
| Target end date (Advanced Roadmaps) | |
| Team | Copied - but not for subtasks since they always take the value from a parent instead of a template. |
| Time tracking | |
| URL Field | |
| User Picker (single or multiple) | |
| Version Picker (single or multiple) | |
These fields are supported when you use Create from template on the native Jira Create screen
| System field | Copied / special handling or exceptions |
|---|---|
| Assignee | |
| Checkboxes | |
| Components | |
| Date picker | |
| Date time picker | |
| Description | |
| Due date | |
| Fix versions / Affects versions | |
| Labels | |
| Number field | |
| Paragraph | |
| Priority | |
| Radio buttons | |
| Reporter | |
| Select list (cascading) | |
| Select list (multiple) | |
| Select list (single) | |
| Summary | |
| Target end | |
| Target start | |
| URL field | |
| User picker (single) | |
| User pickle (multiple) | |
Not supported fields:
Custom fields that are set by Jira and can’t be edited by Issue Templates:
Jira Service Management fields that can only be set by JSM:
