Transition parent issue

This post-function is obsolete. While you may continue using this post function, which will not be removed from JMWE, we recommend you use the more powerful Transition issue(s) instead for new automations.

A workflow post-function that triggers a transition on the parent issue of the current issue.To add the 'Transition parent issue' post-function to a transition :

Click Edit for the workflow that has the transition you wish to add the post-function on.
In the Workflow Designer, select the transition.
Click on Post Functions in the properties panel.
Click on Add post function.
Select Transition parent issue from the list of post-functions.
Click on Add to add the post-function on the transition.
Specify transition(s) either in the table or as a result of the calculated Nunjucks template. See below for more information.
Click on Add to add the post-function to the transition.
After adding, move the post-function to the appropriate position according to Placing post-functions in a transition document.

Common to all post-functions:

Specific to this post-function:

Related links

For information on where the post-function needs to be placed on a transition, see Placing post-functions in a transition.

Refer to the Use cases for the post-functions page for use cases for this post-function.

Refer the Troubleshooting and Support page if the post-functions does not seem to be working as you would expect.

When you add this post-function to a transition and trigger the transition on an issue, the add-on will transition its parent issue using the specified transition, assuming it is valid for the parent issue's current status and available to the current or selected user.

Transition(s)

Trigger one of the following transitions

Input the transition name(s) or id(s) and optionally the workflow name manually or using the Transition picker. If you do not specify the workflow name (manually) the app will not check for a specific workflow. The app triggers the first transition specified in the table that is applicable to the issue in context.

To pick a transition using the Transition picker:

Click on Transition picker
Choose a workflow from Workflow name
Select a transition from the list of transitions displayed
Finally, click on either
- Use Transition Name - recommended if you want the post-function to search for the transition to trigger by name, which is useful when targeting multiple workflows.
- Use Transition ID - if you want to differentiate between transitions that bear the same name.
Click on Add.

To remove a transition: Click on the Remove link for the specific transition

To reorder transitions: Select and move the transition in the table to reorder the list

Trigger a calculated transition

Input a Nunjucks template that returns one or more transition name(s) or id(s) and optionally the workflow name. To specify a workflow name, write a Nunjucks template that returns the transition name or ID along with the workflow name separated by @@. For example: Done@@HR workflow.

To return multiple transitions, write a Nunjucks template that returns transition names or IDs each on a separate line. For example:

2@@Default Jira Workflow
Done@@Another workflow
Close

Example of a template returning transition name:

{%if issue.fields.priority.name == "Blocker"%}
  Escalate
{% else %}
  Assign
{% endif %}

Run As

Run as current user: The current user will be the author of the transition triggered by the post-function.

Run as add-on user: The add-on user will be the author of the transition triggered by the post-function.

Run as this user: Any user specified in this field will be the author of the transition triggered by the post-function.

Transition screen

If the transition uses a transition screen you might want/need to provide a value for fields (such as Resolution) present on the screen. Look below to know how to add/set/remove fields.

To add a field : Select a field from the list of fields and click on Add.
To Remove an added field : Click on Remove to remove a field.
To Set a field value :
- Copy value from current issue : Copies the field value(s) from the subtask.
- Set field value to : You can set the field to a specific value, wherein the value can also include Nunjucks annotations.
  For example : To set the Resolution to Fixed, you can specify Fixed in the value box.

Likewise, you might also want to provide a comment during that transition. This will only work if the triggered transition is associated with a transition screen.

Comment : adds a comment to the parent issue being transitioned. The Comment can be any simple text, e.g. This is a comment. You can also use Nunjucks annotations in the comment using variables. To find out more about the variables, see Using Nunjucks Templates.
Comment visibility :
- Restrict to Group : Restricts the visibility of the comment to a specified group. When you select a valid group name in the Restrict to Group field, the comment will be visible only to the members of the specified group. For no restriction, leave the field blank.
- Restrict to Project Role : Restricts the visibility of the comment to a selected project role. When you select a project role from the drop-down Restrict to Project Role field, the comment will be visible only to the members of the selected project role. For no restriction, leave the field blank.
- Restrict to Internal (Jira Service Desk only) : Restricts the visibility of the comment to the Service Desk Agents and Collaborators only.

Conditional execution

To execute this post-function based on the result of a Nunjucks template see Conditional execution.

Delayed execution

Post functions are provided with an option to delay execution for a set number of seconds using the Delayed execution option (Figure 1, right). To delay execution, select the number of seconds to wait until the post-function is run; any value between 1 second (the default) up to a maximum of 20 seconds can be selected.

Workflows that depend on post functions being executed in a specific order can fail due to the asynchronous nature of Connect post-functions in Jira Cloud. One workaround is to delay the execution of a post-function, thereby creating a more predictable execution order. For example, on the approval of a Story you want to create sub-tasks and immediately transition them; in this case, you will have to delay the execution of the Transition Linked Issues post-function, so that the sub-tasks are created before they are transitioned. See the sample use case, below.

Where possible, it is recommended to use the Sequence of post-functions post-function or Shared action post-function to execute a series of post-functions in a specific sequence instead of applying a delay.

Sample use cases for Delayed execution

On the creation of a Bug, assign it to a member of the QA team and then add the Assignee to the Watchers.

Steps

Create a QA project role, with the testers as its members.
Add the Assign to role member post-function to the transition Create of the Bug workflow.
Select QA as the project role to look for.

Add the Copy value from field to field post-function to the Create transition of the Bug workflow.
Select Assignee as the From field.
Select Watchers as the To field.
Select the Delayed execution option and select 5 sec from the Delay drop-down.

On the approval of a Story, create subtasks for Development and QA, and transition them to In Progress status.

Steps

Add the Create issue post-function to the Approve transition of the Story workflow.
Select Same as current issue from the Project field.
Select Subtask from the Issue type field.
Select Current issue from the Parent issue field.
Repeat the above steps for the Development subtask.

Add the Transition linked issues post-function to the Approve transition of the Story workflow.
Select Issue Link Type as is Parent of.
Select the Delayed execution option and select 10 sec from the Delay drop-down.

You are viewing the documentation for Jira Cloud.

The options Run as add-on user and Run as this user are useful if the current user doesn't have the permission to transition the parent issue(s).

The transition can be specified by name so that the transition can be found regardless of the parent issue's actual workflow, or by ID if disambiguation is required.