- Creating issue from template
- Button Create from template
- Add field Template to the Create issue screen
- Apply template
- Apply template post function
- Link to Create issue from template
This page provides information about the Scopes.
A scope is a set of fields which will be used during the process of creating an issue from a template. In order to apply a template into an issue, i.e. copy values from template’s fields and e.g. substitute variables, the fields has to be in a scope. The same applies to subtasks.
By default, a new template is configured to inherit scope. It is especially useful when you create epics with many stories and subtasks, and you need the same scope for the whole issues hierarchy. If scope can’t be inherited, default scope will be used.
We recommend configuring a scope at least for your primary templates (those you explicitly select when you apply a template, i.e. epics, primary stories).
If you choose to inherit scope, we will try to use the scope set in the parent issue. This means that all issues under an epic inherit its scope. If you have an epic > story > subtasks structure, then the subtask will inherit scope from the story, but if the story’s scope is also set to (inherit), then the subtask will inherit scope from the epic directly.
Scope inheritance doesn’t work for linked issues, therefore you should explicitly set the scope in each one of them.
Add a new scope
To add a new scope:
Go to the project where you store templates.
From project sidebar, select Project settings > Issue Templates.
Go to the Scopes tab.
Click Add in the left column, under scopes.
The Add scope dialog box appears. Type Scope name.
A new scope is added.
Add fields to the scope
To add a field to the scope:
Make sure that you are under your Templates repository project in tab Scopes.
On the left column on the screen there are your scopes and on the right - fields assigned to the scopes.
Select a scope by clicking on it.
Click the drop-down menu and choose a field, which you want to add to the scope.
Selected field is added to the scope.
When a new template is created, it will be configured to use the default scope. Also, template’s name will be taken from issue’s summary.
The default scope is marked with a “D” in the project configuration. It cannot be deleted, but you can choose any scope to serve as the default scope.
To configure default scope:
- Click More icon.
- Select Set as default.
Selected scope is now configured as default.
If you can’t find the answer you need in our documentation, raise a support request*.