Purpose
Post-function "Transition issues" is used for ordering the execution of a transition in one or more issues. This feature is an alternative to virtual fields "Issue status", "Issue status (delayed writing)", "Execute transition" and "Execute transition (delayed execution)" which is the classic method for executing transitions in Jira Workflow Toolbox.
Post-function "Transition issues" uses the same transition manager as virtual fields above, but with the difference that instead of using the names of statuses or transitions, it uses their internal ID. This has the advantage that the renaming of transitions or statuses will not break your workflow, besides it's more intuitive than virtual field in most cases.
Anyway, virtual fields "Issue status", "Issue status (delayed writing)", "Execute transition" and "Execute transition (delayed execution)" keep working as always, and will keep being irreplaceable for some uses like automatic transitioning of issues newly created by post-function Create issues and sub-tasks.
Available since Jira Workflow Toolbox 2.3.0.
Example: Transition open sub-tasks if the selected resolution of the current issue is set to "Won't do"
Select the transition issue post-function. The following screen shows the configuration page.
Once configured, the transition will look like this:
Configuration Parameters
Target issues
issues that will be transitioned
Action to be performed
Usage Examples
- Automatically close resolved sub-tasks when parent issue is closed
- Automatically close resolved sub-tasks when parent issue is closed (Transition issues)
- Change parent's status depending on sub-task's summary
- Change parent's status depending on sub-task's summary (Transition issues)
- Moving story to "In Progress" when one of its sub-tasks is moved to "In Progress"
- Moving story to "In Progress" when one of its sub-tasks is moved to "In Progress" (Transition issues)
- Moving story to "Ready for QA" once all its sub-tasks are in "Ready for QA" status
- Moving story to "Ready for QA" once all its sub-tasks are in "Ready for QA" status (Transition issues)
- Moving sub-tasks to "Open" status when parent issue moves to "In Progress"
- Moving sub-tasks to "Open" status when parent issue moves to "In Progress" (Transition issues)
- Transition only a sub-task among several ones
- Transition only a sub-task among several ones (Transition issues)
- Transition sub-tasks when parent is transitioned
- Transition sub-tasks when parent is transitioned (Transition issues)
- Triage Jira Service Desk email requests (Move issues)
- Automatically close resolved sub-tasks when parent issue is closed
- Automatically close resolved sub-tasks when parent issue is closed (Transition issues)
- Change parent's status depending on sub-task's summary
- Change parent's status depending on sub-task's summary (Transition issues)
- Moving story to "In Progress" when one of its sub-tasks is moved to "In Progress"
- Moving story to "In Progress" when one of its sub-tasks is moved to "In Progress" (Transition issues)
- Moving story to "Ready for QA" once all its sub-tasks are in "Ready for QA" status
- Moving story to "Ready for QA" once all its sub-tasks are in "Ready for QA" status (Transition issues)
- Moving sub-tasks to "Open" status when parent issue moves to "In Progress"
- Moving sub-tasks to "Open" status when parent issue moves to "In Progress" (Transition issues)
- Transition only a sub-task among several ones
- Transition only a sub-task among several ones (Transition issues)
- Transition sub-tasks when parent is transitioned
- Transition sub-tasks when parent is transitioned (Transition issues)
- Triage Jira Service Desk email requests (Move issues)
