Overview

The Transition related issues post function allows you to execute a workflow transition on sub-task, parent or linked issues when a workflow transition is executed.

Configuration

1. Select the relation type in the Perform action on field to decide if the workflow transition will be executed on sub-task, parent, or linked issues.

   1. If Parent or Sub-tasks was selected, set the Applies to field to decide if the workflow transition will be executed on issues with any or selected issue type. If Selected was set, choose the issue types in case of which the transition will be executed in the Issue types field

   2. If Linked was selected, set the Applies to field to decide if the workflow transition will be executed on issues linked with any or selected issue link. If Selected was set, define the details of the issue link used to link issues on which the transition will be executed:

      1. Set the type of link in the Link type field

      2. Set the direction of link in the Link direction field

2. Select a workflow transition to be executed in the Transition field

3. Select if the post function should be executed by the current or another user in the Action executor field (see User Permissions below)

   1. If you have selected Current user option, the post function will be executed by the user making the workflow transition

   2. If you have selected Another user option, provide a user in the User field, so that the post function will be executed by this user

4. Activate the JQL condition option and define the JQL query that has to be met by the issue in order to execute the post function (e.g. “type = Bug and Priority = Blocker”)

5. Activate the Executor condition option if you want the post function to be executed only if the user is or isn’t in a certain Jira user group or project role

   1. Select if The executor has to be or can’t be a member of a certain Jira user group or project role

      1. Select a Jira user group in the Group field if Group was set in the member of a field

      2. Select a project role in the Project role field if Project role was set in the member of a field

Use cases

• If the story is rejected, its sub-tasks are also rejected