Issue Templates for Jira

Note: First, you have to include the Template field on the target screen. If you’re unsure how to add a field to the screen, click here.

Steps

1. Open project settings.
2. Navigate to Request types.
3. Select request type.
4. Open Request form tab.
5. Click Add field
6. Select Template field.
7. Click Apply.

Template field appears in Hidden fields with preset values section.

1. Click Edit value.
2. Select a Template.
3. Click Set.

Once you generate an issue using the specified request type, the template will be applied automatically. The fields within the template’s scope will be populated with predefined values.

If you no longer need a template but want to keep its issue, turn off the “Use as a template” option in the template settings. The template configuration is stored in the issue property and syncs with the “Template” field option. Simply toggle off “Use as a template” if you decide to stop using it.

Turning off the toggle will hide the template settings panel and remove the template option from the selection list. Turning on the toggle will bring back the settings panel and the template option.

Warning: If you delete the template, the options associated with it will also be deleted, and the template option will be removed from the selection list in all issues created from that template. To keep the options in the Template field, disable the template instead of deleting it.

Yes, the order has changed slightly. We switched to using bulk API to improve performance and avoid hitting REST API rate limits. This was especially important when using large templates. Previously, issues at the epic level were created one at a time, followed by their descendants. Now, all issues at the same level are created together, followed by their children. This means you’ll see all the tasks at the epic level before any of their child tasks.

The order in which the issues are created now would be the same if you sort them by Rank. In the backlog, issues should be sorted and grouped automatically, in the navigator you can sort by Rank as follows:

project = “yourproject” ORDER BY Rank ASC

In order to filter the latest issues, narrow it down using created clause:

created > startOfDay() and project = “yourproject” ORDER BY Rank ASC

In the most common case, it will be the issue type you select on the Create Issue screen for the chosen project. When issues are created in the background, we’ll try to match the issue type from the target project to the best-fitting type from the template.

Issue types matching steps: 

1. By ID – we try to find an issue type from the target project with the same ID as set in the template.
2. By name – useful for next-gen projects, where issue types are local and always have different ID than in other projects.
3. By type – that makes sense for the subtask type. If we can’t find a subtask by ID, we will choose any subtask type from the target project.

There are two ways to create issues from templates: using the “Create from template” button or using the Create Issue dialog box and selecting the template from the Template field. When you use the “Create from template” button, a report with the results is generated at the end. This allows you to easily track whether the subtask creation process was successful or not. In the case of using Jira Create Issue dialog box, after clicking on the Create button we are immediately transferred to the newly created issue. Usually, it takes a few seconds for sub-tasks to be created from the parent template.

Go to the Manage templates screen and check the “Used scopes” column in the table.

This feature doesn’t work on the default Create issue screen. That’s why we have the “Create from template” button, which opens a form that is automatically populated after you select the template.

Yes, dynamic variables work with subtasks. The values you provide when creating the issue will be substituted for the dynamic variables in the subtasks. To make dynamic variables work with subtasks, they must also be declared in the root template (the template from which you create the issue). This is because dynamic variables are only collected from the root issue, and the input fields for entering variable values are only displayed for the root issue. Once a variable is declared in the root issue, you can use it freely in other issues, such as subtasks, stories, and linked issues.

Steps:

1. Go to Jira Settings.
2. Click Issues.
3. Click Issue types.
4. Choose the Issue type by clicking Edit.

Your Issue type ID is in the link address.

To address this, access the Scopes settings under Templates Repository project settings. You can also use the Template configuration panel to determine the fields that should be copied.

Yes, just enable the “Allow Customers to use templates via customer portal” option in the global configuration.

Go to Jira settings → Apps → Issue Templates configuration. Open the UI visibility tab, and adjust the groups’ selection for displaying the link.

Issue Templates for Jira Cloud app doesn’t keep user-specific information. It only stores instance description and identification data required for authentication during installation. The app follows standard data protection procedures per Atlassian’s guidelines, using SSL protocol to encrypt data transmission. This includes templates, issues, project configuration, and user-executing templating process information.