...
| Table of Contents |
|---|
Overview
Substitution variables provide powerful capabilities to customize. These variables provide text string representations of fields useful for inclusion in other fields and you can:
Set field values from other existing fields and custom field values.
Construct conditioning values.
The syntax for referencing substitution variables is: %<variable name>%. All text entry fields support replacement.
Example: %parent_summary%
...
Terminology
Term | Definition |
|---|---|
original | The issue being cloned. This is the original issue that started the clone operation. |
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 issue being created as the clone. This could be the main issue or a subtask depending on when entry is being evaluated. |
Variables
Substitution Variable | Description |
|---|---|
<customfield name> parent_<customfield name> | Parent issue's custom field value Recommend using prefix qualified name for clarity |
<customfield_id> parent_<customfield_id> | Parent issue's custom field value |
jql_result_count | Number of issues returned by the query |
jql_result_list | Comma separated list of issue keys returned from the query |
original_<customfield name> | Original issue's custom field value |
original_<customfield_id> | Original issue's custom field value |
parent_affected_versions, original_affected_versions | Comma separated list of affected version names |
parent_assignee, original_assignee | Assignee user id |
parent_components, original_components | Comma separated list of components |
parent_created, original_created | Created date in Jira complete date/time format or a specific format |
parent_description, original_description | Description |
parent_duedate, original_duedate | Due date in Jira DMY date format or a specific format |
parent_environment, original_environment | Environment |
parent_fixed_versions, original_fixed_versions | Comma separated list of fixed version names |
parent_id, original_id | Issue numeric id |
parent_issuetype, original_issuetype | Issue type |
parent_key, original_key | Issue key |
parent_labels, original_labels | Blank separated list of labels |
parent_original_estimate, original_original_estimate | Time spent on the issue in minutes |
parent_priority, original_priority | Priority |
parent_project_name, original_project_name | Project name for the issue |
parent_reporter, original_reporter | Reporter user id |
parent_resolution, original_resolution | Resolution |
parent_resolution_date, original_resolution_date | Resolution date in Jira complete date/time format or a specific format |
parent_security_level, original_security_level | Security level name |
parent_sprint, original_sprint | For a Sprint custom field, set the sprint value using the specified substitution variables when the parent/original issues have one or more sprints assigned. |
parent_status, original_status | Issue status |
parent_summary, original_summary | Summary |
parent_updated, original_updated | Update date in Jira complete date/time format or a specific format |
parent_votes, original_votes | Number of votes for the issue |
parent_watches, original_watches | Number of watchers of the issue |
user_id | User id of the user that is considered to be doing the clone |
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.