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.
Constructing conditioning values.

The syntax for referencing substitution variables is: %<variable name>%. All text entry fields support replacement.

Example: %parent_summary%

Prior 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.

Terminology

Term	Definition

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.

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.

Variables

Substitution Variable	Description

Substitution Variable	Description
user_id	The user ID of user doing the operation.
user_name	The display name of user doing the operation.
now	The current date/time in Jira complete date/time format or a specific format.
project, parent_project, original_project, entry_project	The project key of the issue.
project_id, parent_project_id, original_project_id, entry_project_id	The project ID (numeric) of the issue.
project_category, parent_project_category, original_project_category, entry_project_category	The project category name for the project of the issue.
project_lead, parent_project_lead, original_project_lead, entry_project_lead	The user ID of the project lead.
project_default_security, original_project_default_security, entry_project_default_security	The default issue security level name for the project.
project_default_security_id, original_project_default_security_id, entry_project_default_security_id	The 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	The user ID calculated from the project and components of a issue together with the project configuration used to determine the assignee for newly created issues.
parent_components, original_components, entry_components	The comma separated list of components.
parent_component_descriptions, original_component_descriptions	The comma separated list of components.
parent_affected_versions, original_affected_versions	The comma separated list of affected version names.
parent_fixed_versions, original_fixed_versions	The comma separated list of fixed version names.
parent_subtasks, original_subtasks	The comma separated list of subtask issue keys.
parent_duedate, original_duedate, entry_duedate	The due date in JIRA DMY date format or a specific format.
parent_created, original_created	The created date in JIRA complete date/time format or a specific format.
parent_updated, original_updated	The update date in JIRA complete date/time format or a specific format.
parent_resolution_date, original_resolution_date	The resolution date in JIRA complete date/time format or a specific format.
parent_resolution, original_resolution	Resolution.
parent_labels, original_labels	The blank separated list of labels.
parent_labels_comma_separated, original_labels_comma_separated	The comma separated list of labels.
parent_watchers, original_watchers	The comma separated list of watcher user IDs.
parent_watches, original_watches	The number of watchers of the issue.
parent_votes, original_votes	The number of votes for the issue.
parent_time_spent, original_time_spent	The time spent on the issue in minutes.
parent_estimate, original_estimate	The current (remaining) estimate for the issue in minutes.
parent_original_estimate, original_original_estimate	The original estimate for the issue in minutes.
parent_security_level, original_security_level	The name of the security level.
<field name>	The Jira issue field name of the parent issue. Deprecated but still active, recommend using specific replacements variables for clarity.
<customfield name> parent_<customfield name>	The custom field name of the parent issue.
<customfield id> parent_<customfield id>	The custom field ID of the parent issue.
original_<customfield name>	The custom field name of the original issue.
original_<customfield id>	The custom field ID of the original issue.
group_<group name>	The comma separated list of user IDs for members in the group.
role_<role name>	The 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>	The 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>)	The comma separated list of cascade select child option values for the specific parent value provided
function_<function name>(<parameter>) earliestUnreleasedVersion(projectKey) latestReleasedVersion(projectKey) versionId(projectKey, versionName)	The 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.