This post function automatically executes a specific transition on the selected issues or transitions issues to a selected status

It is the preferred way of executing transitions. However, in some cases, e.g. the automatic transitioning of newly created issues using the Create issue post function, users might want to use the following alternative field codes:

Configuration

Target issue

Select the issue(s) to be transitioned. The following options are available:

OptionDescription
Current issueThe current issue will be transitioned.
Parent issueThe current issue's parent will be transitioned.
Sub-tasksThe current issue's sub-tasks will be transitioned. If you choose this option you can further filter your selection (e.g. by issue type or status). Only useful for standard issues
Sibling sub-tasksThe current issue's sibling sub-tasks will be transitioned. Only useful if the current issue is a sub-task
Linked issuesLinked issues will be transitioned. If you choose this option you can further filter your selection (e.g. by issue type or status). 
Linked epicThe related epic will be transitioned.
Issues under epicAll issues related to the same epic will be transitioned. If you choose this option you can further filter your selection (e.g. by issue type or status). 
Sibling issues under epicAll sibling issues related to the same epic will be transitioned. If you choose this option you can further filter your selection (e.g. by issue type or status). 
Set target issue manually (parser expression)

Define the issues that will be transitioned by defining an expression. The JQL mode and Issue list mode are available.

The expression must return either a valid JQL expression or an issue list with issue keys.

Mode

Select the transition to be executed or the status to be transitioned to. The following options are available:

OptionDescription
Execute transition

Either select an existing transition from any available workflow or set the transition manually using a parser expression in Basic text mode.

The expression must return a transition name.

Transition to status

Either select an existing status from any available workflow or set the status manually using a parser expression in Basic text mode.

The expression must return a status name.

If more than one transition is available to reach the configured status, the first transition (found by Jira) will be executed.

Both, transition or target status, have to be available from the issues' current status. The provided list, however, contains all statuses and transitions in the system.

Additional options

Choose between the following options (multi choice is possible):

OptionDescription
Ignore conditions

Existing conditions in the transitions to be executed will be ignored.

Ignore validators

Existing validators in the transitions to be executed will be ignored.

Ignore project permissions

The "Transition Issues" project permission will be ignored for the user running this post function.
Delayed execution

The execution of this post function will be delayed by the value specified in milliseconds.

This parameter is useful, when multiple operations have to be performed in a single transition. The delayed execution ensures that all previous operations have been completed, e.g. field values that are referenced in this post function are present.

The maximum delay is 60,000 milliseconds (60 seconds).

Conditional execution

You can optionally specify a logical expression to define the circumstances (or conditions) under which the post function should be executed.

The result of the logical expression must return a boolean value of either:

  • true → the post function will be executed
  • false → the post function will not be executed

Using the conditional operator, even complex or multi-layered conditions can be constructed.

Make sure to learn more about defining logical expressions and browse through the various examples here: Logical mode

Run as

Select which user will be used to execute this post function. By default this parameter is set to the current user. You can also use field codes to run the function as a dynamic user (e.g. current assignee).

Make sure that the user running the post function has all the relevant permissions to perform the actions defined in the configuration (e.g. "Update Issues")!

If you want to keep track the actions being performed automatically, we suggest to create a dedicated JWT account, granted all relevant permissions, and use it in the Run as parameter to identify which changes have been made with JWT.



If you still have questions, feel free to refer to our support team.