Substitution variables

On this page

Description

Substitution variables provide powerful capabilities to customize the creation of issues. Variables provide text string representations of fields useful for inclusion in other fields.

  1. Setting field values from other fields and custom field values.
  2. Constructing conditioning values.
  3. For multi-issue creation scenarios.

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

Example: %parent_summary%

The Create Issue and Create Sub-task and post functions use the following terminology. The terminology is also used in substitution variables.

Term

Definition

original

The original issue that started the workflow transition. This could be an issue or sub-task.

parent

The parent issue of the original issue. If the original issue is not a sub-task, then parent is the same as original.

entry

The issue currently being created and processed.

entry_parent

The parent of the sub-task entry being created. Available only when creating sub-tasks for an issue that is different than the parent of the original issue.

sibling

A sibling issue is a sub-task with the same parent as the original issue. In this case, the Create Sub-task post function may optionally create a sibling of the original issue.

Variables

Some variables are listed on the post function definition screen as an aid when creating definitions. This is a more complete and detailed list and represents the variables available with the most recent version of the add-on. If you need access to additional fields, raise a support request with our support team.

Note the terminology for the meaning of parent and original.

Custom fields

Custom fields are identified by name or id (like customfield_12345). By name is easier to know what it is referring to but by id will survive renaming a custom field.


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.

Log a request with our support team.

Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.