Transition related issues

Introduction


Complex element

This workflow element is complex and maybe a little confusing for beginners. If you have any further questions, please contact us via our Customer Portal.


This post function allows you to transition-related issues. For example, this post function can be used in the following scenarios:

  • Resolve subtasks when a parent is resolved.
  • Close all linked issues.
  • Start progress on a parent when the Start progress is executed on one of its subtasks.
  • Unassign all unresolved issues from the current issue assignee (e.g. when he/she goes on holiday).

Please note that the automatic transition may fail if a validator or a condition was added. The transition screen will not be shown, so it's not possible to update issue fields with new values.

Element summary
Status
CURRENT
Version compatibility6.0.1 - Latest
SupportedYes
Introduced in version1.0.0

Post function parameters

 This post function takes the following parameters:

  • Issue relation and JQL - described at the bottom of the page.
  • Which transition - a method of transition selection.
    • Transition by name or id - simply enter the name or ID of the transition (it must be available in the current related issue state).
    • Transition to status - select a destination status and a post function to execute the first matching transition (try until the first transition is successful).
  • As a user - select a user who will perform the transition. If empty, then the current user is used. It can be useful when you are trying to transition issues from other projects where the current user is not permitted to act.

Working with related issues

Related issues can be selected by using two inputs:

Issue Relation - where you can choose a relation with the current (transitioned) issue;

JQL - you can put your JQL text to filter some issues from the results. If you leave the JQL Field empty, all issues in a given relation are taken into account.

In the example above you wanted to execute a workflow function on subtasks of the current issue and take additionally only the ones with the "Sub-task" and priority="High" type.

Tags

In the JQL field you can put some text tags to be replaced with actual values of the current (transitioned) issue:

TagDescription

$$CURRENT_DATETIME$$

The current date and time.
 $$CURRENT_USER$$The name (login) of the current user.
$$ISSUEKEY$$The key of the current issue.
 $$ISSUEID$$ID of the current issue.
 $$REPORTER$$The current issue reporter's name.

$$ASSIGNEE$$

The current issue assignee's name
$$PROJECTKEY$$The project key.
$$CURRENT_STATUS$$The current issue status.
$$ISSUETYPE$$The issue type.
$$CREATED_DATE$$The date when the issue was created.

$$CURRENT_STATUS_CATEGORY$$

A status category of the current issue (To Do, In Progress or Done).
$$TRANSITION_NAME$$The name of an actual transition (doesn't work in Conditions)
$$TRANSITION_ID$$ID of an actual transition (doesn't work in Conditions).
$$TRANSITION_COMMENT$$The content of a transition comment (doesn't work in Conditions).

The JQL field has a built-in validation feature. If your query is incorrect, you will see a red sign next to the JQL field and an error description as shown below:

Example of use