Description
Substitution variables provide powerful capabilities to customize. Variable 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.
The syntax for referencing substitution variables is: %<variable name>%. All text entry fields support replacement.
Example: %parent_summary%
Info |
---|
Legacy substitution supportPrior to Release 3.0, a more restrictive variable substitution was provided using @<variable name>@ syntax with either no prefix or parent_ prefix. This is deprecated in 3.x, but still supported to help migrate to the newer support. You should migrate older customizations to the new support when it is convenient. Legacy replacement support will be removed in release 5.x. Only a limited set of variables were available using this support using the JIRA internal defined name: issuekey, summary, description, assignee, reporter, fixVersions, versions, components, labels, security. |
Include Page | ||||
---|---|---|---|---|
|
Variables
Note the terminology for the meaning of parent and original. Many of these values are unlikely to be needed for clone customization but are provided for consistency with Create on Transition for Jira and Update on Transition for Jira variables.
Variable | Description |
---|---|
user_id | User id of user doing the action |
user_name | Display name of user doing the action |
now | Current date/time in JIRA complete date/time format or a specific format |
project, parent_project, original_project, entry_project | Project key of the issue |
project_id, parent_project_id, original_project_id, entry_project_id | Project id (numeric) of the issue |
project_category, parent_project_category, original_project_category, entry_project_category | Project category name for the project of the issue |
project_lead, parent_project_lead, original_project_lead, entry_project_lead | User id of the project lead. |
project_default_security, original_project_default_security, entry_project_default_security | Default issue security level name for the project |
project_default_security_id, original_project_default_security_id, entry_project_default_security_id | Default issue security level id for the project |
parent_key, original_key | Issue key |
parent_id, original_id | Issue numeric id |
parent_summary, original_summary, entry_summary | Summary |
parent_description, original_description, entry_description | Description |
parent_environment, original_environment, entry_environment | Environment |
parent_issuetype, original_issuetype, entry_issuetype | Issue type |
parent_status, original_status | Issue status |
parent_priority, original_priority, entry_priority | Priority |
parent_reporter, original_reporter, entry_reporter | Reporter user id |
parent_assignee, original_assignee, entry_assignee | Assignee user id |
parent_automatic_assignee, original_automatic_assignee, entry_automatic_assignee | User id calculated from the issue's project and components together with the project configuration used to determine the assignee for newly created issues |
parent_components, original_components, entry_components | Comma separated list of components |
parent_component_descriptions, original_component_descriptions | Comma separated list of components |
parent_affected_versions, original_affected_versions | Comma separated list of affected version names |
parent_fixed_versions, original_fixed_versions | Comma separated list of fixed version names |
parent_subtasks, original_subtasks | Comma separated list of subtask issue keys |
parent_duedate, original_duedate, entry_duedate | Due date in JIRA DMY date format or a specific format |
parent_created, original_created | Created date in JIRA complete date/time format or a specific format |
parent_updated, original_updated | Update date in JIRA complete date/time format or a specific format |
parent_resolution_date, original_resolution_date | Resolution date in JIRA complete date/time format or a specific format |
parent_resolution, original_resolution | Resolution |
parent_labels, original_labels | Blank separated list of labels |
parent_labels_comma_separated, original_labels_comma_separated | Comma separated list of labels |
parent_watchers, original_watchers | Comma separated list of watcher user ids |
parent_watches, original_watches | Number of watchers of the issue |
parent_votes, original_votes | Number of votes for the issue |
parent_time_spent, original_time_spent | Time spent on the issue in minutes |
parent_estimate, original_estimate | Current (remaining) estimate for the issue in minutes |
parent_original_estimate, original_original_estimate | Original estimate for the issue in minutes |
parent_security_level, original_security_level | Security level name |
<field name> | Parent issue's JIRA issue field name Deprecated but still active, recommend using specific replacements variables for clarity |
<customfield name> parent_<customfield name> | Parent issue's custom field name Recommend using prefix qualified name for clarity |
<customfield id> parent_<customfield id> | Parent issue's custom field id |
original_<customfield name> | Original issue's custom field name |
original_<customfield id> | Original issue's custom field id |
group_<group name> | Comma separated list of user ids for members in the group |
role_<role name> | Comma separated list of user ids for users that are role actors for the project of the original issue |
values_<customfield name> values_<customfield id> | Comma separated list of custom field option values in the context of the original issue |
values_<customfield name>(<value or sub variable>) values_<customfield id>(<value or sub variable>) | Comma separated list of cascade select child option values for the specific parent value provided |
function_<function name>(<parameter>)
| Functions that derive useful text values that can be used as substitution variables. Some are similar to their equivalent JQL function (follow link). The parameter(s) may be a substitution variable. |
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.