Introduction
This post function allows you to transition related issues.This post function can be used for example in following scenarios:
- Resolve subtasks when parent is resolved
- Close all linked issues
- Start progress on parent when Start progress is executed on one of its subtasks
- Unassign all unresolved issues from current issue assignee (e.g. when he/she goes holiday)
Please note that automatic transition may fail if a validator or condition was added. Transition screen will not be shown, so it's not possible to update issue fields with new values.
| Element summary | |
|---|---|
| Status | CURRENT |
| Version compatibility | 6.0.1 - Latest |
| Supported | Yes |
| Introduced in version | 1.0.0 |
Post function parameters
Post function takes following parameters:
- Issue relation and JQL - described at the bottom of the page
- Which transition - method of transition selection
- Transition by name or id - simply enter name or ID of transition (it must be available in current related issue state)
- Transiton to status - select destination status and post function execute first matching transition (try until first transition is successful).
- As user - select user who will perform the transition. If empty then current user is used. It can be useful when you try to transition issues from other projects where 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. In the JQL field you can put some text tags to be replaced with actual values of the current (transitioned) issue: $$CURRENT_DATETIME$$ $$ASSIGNEE$$ $$CURRENT_STATUS_CATEGORY$$ 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:
Tags
Tag Description 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. 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. 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). 
Example of usage
