On this page
Description
Substitution variables provide powerful capabilities to customize. 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 constructing a list of issues to be updated.
The syntax for referencing substitution variables is: %<variable name>%. All text entry fields support replacement.
Example: %parent_summary%
The functions use the following terminology. The terminology is also used in the substitution variables.
Term | Definition |
---|---|
original | The original issue that started the workflow transition. This could be an issue or subtask. |
parent | The parent issue of the original issue. If the original issue is not a subtask, then parent is the same as original |
entry | The current entry being processed from the issue list |
Variables
Some variables are listed on the post function definition screen as an aid when creating definitions. This is a more complete and detailed list and represents the variables available with the most recent version of the add-on. Create an issue if you need access to additional fields.
Note the terminology for the meaning of parent and original.
Variables used by post functions versus validators
- Post functions are more likely to use field variables either from the original issue or parent issue as they represent the already changed values (post transition)
- Validators are more likely to use the transition variables to access the screen values since the issue field values still represent the former values
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.