.png?version=1&modificationDate=1657805719617&cacheVersion=1&api=v2&width=272&height=48)
On this page
Description
Substitution variables provide powerful capabilities to customize the creation of issues. Variables provide text string representations of fields useful for inclusion in other fields.
- Setting field values from other fields and custom field values.
- Constructing conditioning values.
- For multi-issue creation scenarios.
The syntax for referencing substitution variables is: %<variable name>%. All text entry fields support replacement.
Example: %parent_summary%
The Create Issue and Create Sub-task and post functions use the following terminology. The terminology is also used in substitution variables.
Term | Definition |
|---|---|
original | The original issue that started the workflow transition. This could be an issue or sub-task. |
parent | The parent issue of the original issue. If the original issue is not a sub-task, then parent is the same as original. |
entry | The issue currently being created and processed. |
entry_parent | The parent of the sub-task entry being created. Available only when creating sub-tasks for an issue that is different than the parent of the original issue. |
sibling | A sibling issue is a sub-task with the same parent as the original issue. In this case, the Create Sub-task post function may optionally create a sibling of the original issue. |
Substitution Variables
Several example substitution variables are listed on the post function screen as an aid when creating definitions. However, the table below contains a more complete and detailed list of substitution variables available as you work with the Create Issue or Create Sub-task post function.
Table containing valid substitution variables and their descriptions.
Working with Custom Fields
Custom fields are identified by either name or id (e.g., customfield_12345). Referencing a custom field by its name is often easier to know what the value is referring to. Yet, by referencing custom fields by their id will allow the configuration to survive the renaming of a custom field.
Configured date format
For date substitution variables, the format of the replacement variable can be specified if the default format is not desirable. The format is specified by a Simple Date Format string enclosed in parenthesis following the substitution variable name. For example: %created(yyyy-MM-dd)% will result in replacement like 2013-05-28.
