Using System Variables

As mentioned before, variables - are the placeholders that are automatically filled with the data that is available at the moment of the issue creation. The list of SYSTEM Variables is placed on the ‘Manage Variables’ page in the ‘SYSTEM’ section.

For easy access to the documentation click the info link next to the SYSTEM section

System Variables can be used for specific fields.

Date and Time variables work for the Epic Name, Summary, Description, Labels (doesn’t work for $dateTime in case there are spaces between the words), Environment, and Due Date (doesn’t work for $time) fields. If you use $dateTime for the Due Date field after applying you’ll observe the date value and no time value.

• $yesterday for the yesterday date displaying works after the issue was applied

• $lastDayOfMonth for the last day of the current month shows after the issue was applied

• $today for today’s date displaying works after the issue was applied

• $tomorrow for tomorrow date works after the issue was applied

• $nextWeek for the day a week later after the issue was applied

• $time for the exact time when the issue was applied

• $dateTime for the current date and current time when the issue was applied

  

  

  

Current User variables work for the Epic Name, Summary, Reporter (only for $username in Templates), Description, Environment, Labels (works in case there are no spaces between the words), Assignee (only for $username in Templates) fields.

• $username for the username who is applying the template or hierarchy

• $userEmail for the email address of the user who is applying the template or hierarchy

Current Issue Details variables work for the Epic Name, Summary, Description, Reporter (works only for the $projectLeadName), Assignee (works only for the $projectLeadName), Labels (works in case there are no spaces between the words) fields.

$issueKey works for hierarchies with the Summary and Description fields.

• $projectKey for the current project key where the issue was applied

• $projectName for the current project name where the issue was applied

• $projectLeadName for the current project leader name where the issue was applied

• $issueKey for the current issue key that was applied

Parent Issue Details variables are to be used only in hierarchies for the child issues. They work in the Summary, Description, and Environment fields.

• $parentKey for the key of the parent issue

• $parentSummary for the summary of the parent issue

• $parentDescription for the key of the parent issue

• $parentIssueType for the issue type of parent issue

• $parentStatus for the status of the parent issue

• $parentPriority for the priority of the parent issue

• $parentDueDate for the due date of the parent issue

Please Note!

The ‘Labels’ field has a restriction for using the spaces inside the labels. If the data includes a space in the text, the System Variables will not show the proper value, and the variable itself will be shown after applying the issue.

For any questions or feature requests contact us via the Customer Portal

Or drop us an email at support@appsdelivered.atlassian.net. If you are using this option, please check your junk folder regularly, as our reply can be placed there by your email service.

Before submitting a bug report or support ticket, please update to the latest version of the add-on.

Please add information about the version of Jira and the add-on.