...
Description
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%
...
| Include Page | ||||
|---|---|---|---|---|
|
...
Variables
...
| sortColumn | 1 |
|---|
...
parent_key, original_key
...
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_ |
...
<customfield name>
parent_<customfield name> (since 3.4)
...
Parent issue's custom field value
Recommend using prefix qualified name for clarity
...
<customfield_id>
parent_<customfield_id> (since 3.4)
...
original_<customfield name>
...
original_<customfield_id>
...
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.