By using the parent
expression, you can easily configure nested (child) templates to inherit values provided in the parent.
This can be useful when you need to set the same component, version or labels in all epic’s issues and want to use the same template in different scenarios.
Just enter a field value in the Create issue dialog. All children created from the primary template inherit the given value.
To use the parent
accessor issues need to be in a parent-child relation, for example children of an epic or subtasks. Linked issues don’t have such a relation.
If you want to pass down values from your primary issue (issue from which the templating process starts), you can use the primaryIssue
accessor.
primaryIssue
- will access a field for which it is configured
primaryIssue.fix_versions
- provides a short form of a field name with _
instead of space in case you want to configure it for other field, for example, Affects Versions
primaryIssue.field("Fix versions")
- use a field expression with an exact name if your field contains special characters
primaryIssue.customfield_10330
- use a custom field key in case you have more than 1 field with the same name
With the expression variable("variable name")
you can use values provided with Dynamic variables in custom/system fields. You can refer variables in all children and linked issues.
This can be useful when you want to set the same value across the whole structure, and at the same time you want to use variables for the same value in different fields, for example as a part of a summary or description. This approach is much more flexible than using a simple parent expression.
Supported actions:
:user
type dynamic variable, all user type fields are supported, for example, assignee, reporter, user pickers:date
or :datetime
variable to a date or a datetime field type, for example, Due date, Start date, Date Picker, Date Time Picker, etc.Value of any field can be computed using vast Smart expressions.
Expressions that can be used depend on the type of field against which you are calculating the value, for example, a user field, like reporter, can be set to project lead by the project.lead
expression.
You can set a reporter to the project lead using - project.lead