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.
To create set of fields:
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 Create Structure post function. (The connection between story and epic will be reproduced automatically in this case, so adding Epic link to your 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).
If you’d like to use either the Component or the Fix version field, please keep in mind that their values must be identical in both projects (in the Template Repository project and in your target project where the template is applied).
Here is how you can further configure your set of fields:
You can choose to overwrite the field contents with values defined in a template. It is particularly useful when you want to apply a different template on the Edit screen or upon a workflow transition. This way, different fields from different templates can be available for users on different stages of the issue lifecycle.
Overwriting values also means that when users type in anything else in those fields, it will be replaced by values provided in the template. As it might seem confusing for users, a special warning is displayed on screens where such a template is applied:
If you don’t want a template to overwrite field values but it does replace them anyway, you may try following configurations:
To disable overwriting values entirely:
If you only want some fields to be autofilled in the background, you may use a separate set of fields for that:
Switch on an Alternative source to start configuring each field. A pop-up window appears.
In Alternative source there are fields, that have additional options:
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.
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.
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.
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.
If you can’t find the answer you need in our documentation, raise a support request.
If you can’t find the answer you need in our documentation, raise a support request.