Apps documentation
Issue Templates for Jira
Cloud Server/Data Center
Issue Templates for Jira


Server/Data Center

Last updated May 13, 2021


Which issue type will be used to create an issue from my template?

In the most basic scenario, it will be the issue type you can select on the Create Issue screen for the chosen project. For issues created in the background, we will try to choose the best matching issue type from the target project.

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.

Is it possible to configure default template for a particular request type?

Yes, it’s possible to define a template that will be automatically applied to the selected request type.

Before you start, you need to add Template field to the target service screen. If you’re not sure how to add field to the screen, click here.


  1. Open project settings.
  2. Navigate to Request types.
  3. Select request type and click Edit fields.
  4. Click Add field.
  5. Select Template field.
  6. Click Apply.
    Template field appears in Visible fields section.
  7. Click Hide.
  8. Select a Template.
  9. Click Set.


As soon as you create issue from the request type, template will be automatically applied. Fields from template’s scope will be filled with predefined values.

Fields from the Scope will be overwritten. Make sure not to overwrite fields provided by user.

I can’t see template’s sub-tasks in issue created from template.

We can create issues from templates in two ways:

  • by using Create from template button and
  • by using Create Issue dialog box (and selecting template from the Template field afterwards)

While using Create from template, a report with results is generated at the end. Thanks to that, we can easily track if the process of creating sub-tasks is completed or has failed.

In case of using Jira Create Issue dialog box, after clicking on Create button we are immediately transferred to newly created issue. Usually, it takes few seconds for sub-tasks to be created from the parent template.


If you cannot see the relation between sub-tasks (or sub-tasks are not generated), wait few seconds and refresh the page.

How can I see which scopes are used in particular template?

Go to Manage templates screen and check used scopes in the table.

Why does not a form fill automatically after selecting a template?

This function does not work on the default Create issue screen. That is why we have Create from template button that opens a form which is filled automatically after the template is selected.

Can I turn off a template?

A template cannot be turned off but you can delete template’s configuration. Then the template will not be visible in the dropdown when creating a new issue, but the issue will stay in the repository project. Remember that you can always turn this template on by adding configuration.

Do Dynamic Variables work with sub-tasks?

Yes, Dynamic Variables work with sub-tasks.

Dynamic Variables if used in sub-tasks will be replaced with values provided during creation.
There is one condition to make it work - a variable have to be declared also in a root template (the template from which you create issue). This is because variables are only collected from root issue, which means that input fields, where you fill variables values, will be displayed only for root issue. Once variables is declared in a root issue you can use it freely everywhere, e.g. sub-tasks, stories, linked issues.

When I create issue from template, on the screen with results I see an error: {“errorMessages”:[“The value ‘TEMP’ does not exist for the field ‘project’.”,“No issues have a parent epic with key or name ‘TEMP-12’"],“warningMessages”:[]}.

Go to your Templates Repository project settings and check if Browse projects permissions are granted to atlassian-addons-project-access role.

For more information about configuring Repository for Templates, click here.