Default Template

Learn how to configure default templates for different projects, issue types, and transitions

The Default Template feature allows you to select a template that will be automatically applied to chosen issue types in a project. Here’s what you can configure:

• Issue type: choose what issue type the template should apply to.
• Screen: choose at which point the template should be used (either on the Create or Edit screen, or upon any issue transition).
• Visibility: decide if the Template field should be visible for users.

Configure default templates in a project

Steps

To configure a default template:

1. Open the project where you want use templates and select Project settings.

2. Go to Issue Templates > Default Templates.

   

3. Select the template from the drop-down list.

4. Choose the issue type the template should be associated with.

5. Choose the workflow transition upon which the template should be applied.

   

Result

Selected templates are set as defaults for the defined issue types and will be applied upon chosen transitions (or on selected screens).

Note

If you make a template unselectable in the Availability tab, a warning icon will appear next to the template name.

Default Template on the Customer portal

Default Template allows you to automatically apply selected templates on request forms. You can define a different template for each request type.

Steps

To configure Default Template on the Customer portal:

1. Open your service project and select Project settings.
2. Go to Default Templates in the Issue Templates section.
3. Open the For Jira Service Management tab.
4. Select the template from the drop-down list.
5. Choose the request type.

Result

Selected templates are set as defaults on the Customer portal for defined request types.

Note

If you disable a template in the Availability tab, a warning icon appears next to the template name.

Create a template

Say, we have a software development project called New App, and we’d like to auto-populate all Bug issues with some basic information.

First, we need to prepare a Bug Template that we’ll use as the default template. In order to do so, we need to create it under Issue Templates > Manage Templates:

Select the template as default

Now that our template is ready, we can associate it with the Bug issue type in our project. Let’s go to the New App project settings and select Issue Templates > Default Templates.

There, we’ve got three steps to follow in order to make it work for us:

1. Select the Bug Template from the list.
2. Choose the Bug issue type.
3. Choose the workflow transition. For this simple example let’s choose Create.

Configure template’s editability

The last thing to set up is if the template can be edited. If you don’t want your users to be able to change the template, you may leave this option disabled. Otherwise, you can go to Issue Templates > Configuration > Default Templates and check the box to Allow the change of applied template. This state applies only when an issue uses a default template.

If you don’t set a default template, users can still change values. The template selection field will be visible for a user, but they won’t be able to change it. If a user has variables in this template, they can still fill them.

Result

Depending on the visibility settings, we may have two different results:

1. Default Template is applied automatically in the background and can’t be changed (Allow the change of applied template option is disabled):

   

2. Default Template is applied automatically but users can change it by selecting a different template from the list (Allow the change of applied template option is enabled):