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

Server/Data Center


Release notes
Last updated Aug 27, 2020

Set of fields (Scope)

Learn how to modify your template’s scope.

Templates use fields or/and custom fields, defined by user. You can decide which fields should be auto-filled or copied into your target issues.

Once you create a set of fields, you can re-use it in other templates.

  • In order to access this area you need administrative permissions. Read more about permissions here.
  • Find more information about available fields here.


To create set of fields:

  1. Open your global administration settings.
  2. Click Set of fields in Issue Templates section on the left sidebar.
  3. Click Add below the list of fields.
  4. Add a name for your new Set of fields.
  5. Add fields to the list.
  6. Choose fields from the multiselect list and click Add.
  • Add Epic link to Scope only if you create an issue (story or task) that should be linked to an existing epic.

  • Don’t add it to scope if you are creating a structure of issues using the post function Create Structure, though. (The connection between story and epic will be reproduced automatically in this case, so adding Epic link to Set of Fields might only cause configuration problems).

  • Please remember that the epic you’re linking to must be an actual issue (not a template).

There are few options at the top of each field.

  • By switching on Read-only, you disable editing specific field after autocomplete.
  • While Applying template, Overwrite will automatically replace field’s value in issue with value from template. Switch the toggle to on, if you want to use Overwrite for concrete field.
  • With Alternative source feature, you are able to modify source (template) value by using values from parent or another issue. With Alternative Source you are able to modify source field’s value also by adding postfixes and prefixes.

Alternative Source

Switch on an Alternative source to start configuring each field. A pop-up window appears.

  1. Select no alternative source if you don’t want to change value. Fields will remain the same as in template.
  2. Choose a parent issue, if you’d like to implement values from the parent template.

    Parent issue option is dedicated for sets of fields used in sub-tasks.

    Select a parent issue from which the value will be applied. Add a prefix, in case you want to enter a text before the copied value. Add a postfix, in order to enter a text closing the value.
  3. Other issue option allows to select an issue from which the value will be copied.
    To complete first field, type the Key of target issue. Select a field from which the value will be applied. Add a prefix, in case you want to enter a text before the copied value. Add a postfix, in order to enter a text closing the value.

Useful features

In Alternative source there are fields, that have additional options:

  • Assignee

There’s a random option in Assignee field, which allows to add a random user from given group. Type the name of group to the tab.

  • Attachment

Alternative source allows to copy attachments to issue. Switch the toggle to define an alternative source for attachment. You can re-use it from parent issue or choose one of available in other issue.

  • Due Date

With alternative source, you are able to set the Due Date as in parent or other issue. It is also possible to set the current date to a Due Date field. Type the number to the Shift by tab - given number will be added to the date.

Mapping concepts

While selecting a field in a pop-up window, you can choose another type of field as an alternative source.

For example: you’d like to add a summary to the Set of fields, but re-use a text from another issue’s description. Both fields can be selected from the drop down list, even tough they’re different.

Check the table below to see, which fields are compatible with each other.

Type Compatible field
text Summary, Description, Environment, Textfield (single and multi line)
user Assignee, Reporter, Request participants, User Picker (single and multiple users)
date Due Date, Date Picker, Date Time Picker
other Other fields (custom fields)

Use following mapping scheme, to properly configure your alternative source:

text <- text

user <- user, text

date <- date

x <- x (where x is some custom field)

Configured sets are visible in Set of fields section in Issue Templates Details.

Set of fields in Issue Templates Details

There is also another method to configure Set of fields.

  • Autocomplete

Autocomplete allows to fill in issue fields with pre-defined template values. Once you select a template in issue, all fields from Set of Fields for Autocomplete fill in automatically. Read more about Autocomplete here.

Set of fields used for Autocomplete supports following fields on the Customer Portal: Summary, Description, Due Date, Reporter, Single Select, Text Field, User Picker, Checkboxes, Date Picker, Cascading Select. Read more about Templates in Jira Service Desk here.

In Autocomplete, you are able to choose a Set of fields from the list or create new one.

To add your own Set of fields:
1. Click ‘+’.

2. Type the Name.
3. Choose fields.

Attachments can only be copied by Copy Values post function.

4. Click Save.

  • Copy

Copy allows to fill in fields in new issue with pre-defined values from template. Once the issue passes a concrete transition in workflow, values are automatically copied from the template.

In Copy, you can also use existing Set of fields or create new one. Procedure of creating a Set of fields is the same as in Autocomplete subsection.

  1. Click ‘+’.
  2. Type the Name.
  3. Choose fields.
  4. Click Save.

    For basic configuration, we recommend to use Set of fields for Autocomplete and Copy in Issue Templates Details.

  • Sub-tasks

Each sub-task in template can have own set of fields. You can select a set of fields configured previously or create a new one. Each sub-task can copy different set of fields.


Remember, that Summary is a mandatory field in sub-task’s scope.

Need help?

If you can’t find the answer you need in our documentation, raise a support request*.

*Include as much information as possible to help our support team resolve your issue faster.

Additional reading