🚀Transition Work Items - Post Function

Automatically transition the current issue or related issues (parent, child, or linked) to the next available status in the workflow after a transition.

Overview

With Transition work items, you can:

• Choose related items to work on: Current, Parent, Children, Sub-tasks, or Linked items

  • Filter by issue type or link type

• Choose a destination status

• Choose an actor to perform the work

• Use powerful preconditions from Ultimate Validator

• Set fields during the transition

  • Copy field values from the Parent or other fields

On transition to Done, automatically move all child issues to Done and set their resolution to match the parent.

Settings

Select work items to transition

Pick related items to transition:

• Current issue – Transition the issue being worked on to the next status.

• Parent – Transition the parent issue to the next status.

• Children – Transition direct child issues, including sub-tasks.

• Sub-tasks – Transition issues at the lowest level in the hierarchy.

• Linked issues – Transition issues linked through relations such as blocks or relates to.

For Children, Sub-tasks, and Linked issues, you can narrow the scope by selecting specific issue types. For Linked issues, you can also filter by link type.

Choose destination status

Actor

Defines who is recorded as having made the changes:

• User who transitioned the issue (default)

• Workflow Building Blocks for Jira (app actor)

The selected actor will appear in the issue’s change history.

• User who transitioned the issue – Recommended for most cases; changes are attributed to the actual user.

• Workflow Building Blocks for Jira – Has all permissions needed to evaluate preconditions and edit the issue. Recommended for complex scenarios where permission checks might prevent changes from being applied.

If you would like additional actor options, you can vote for this feature request: More actor options for post functions

Preconditions

Preconditions control whether the post function runs.

• Configure preconditions using the condition builder known from the Ultimate Validator.

• The builder generates a Jira expression, evaluated as the selected Actor.

• The post function runs only if the precondition evaluates to true.

Note: An expression may return different results for different users due to permissions. For example, users may see different comments on the same issue.

Current User option in preconditions

Always represents the actual user who performed the transition, regardless of the Actor setting.

Permission Requirements

• To see groups other users belong to: Administer Jira global permission is required.

• To see roles of other users: Administer Projects permission for the project, or Administer Jira global permission is required.

Provide transition fields

This post function supports editing the following Jira fields:

Text & Selection Fields	All text fields, standard select lists (single and multi-select), radio buttons, checkboxes, URL fields, number fields
User & Group Fields	User picker, team picker, group picker
Issue Metadata	Issue type, priority, resolution, parent, labels, components, project picker
Time Tracking	Original estimate, remaining estimate
Versions & Dates	Version pickers, date fields
Agile	Sprint
Jira Service Management Fields	Request type, request participants, organisations

Understanding Post Functions in Jira

Order of Post Functions

Post functions perform additional processing after a workflow transition is executed.

When multiple post functions are added to the same transition, the execution order is not guaranteed.

Our post functions always operate on the current data at the time they run, including when evaluating preconditions. If multiple post functions modify the same fields and those fields are referenced in preconditions, the results may vary due to the asynchronous nature of post function execution.