Futures used to implement the example
Example: Moving story to "In Progress" when one of its sub-tasks is moved to "In Progress" (Transition issues)
A sub-task for a story is moved from "To Do" to "In Progress". The workflow then automatically moves the story from "To Do" to "In Progress".
Insert Transition issues post-function into transition from "To Do" to "In Progress" in sub-task's workflow with the following configuration:
Text to be parsed is: %{00042} = "To Do"
Note that:
- %{00042} is field code for field Parent's issue status
- If you have a condition or a validator in parent's workflow's transition from "To Do" to "In Progress" that blocks the transition depending on the status of sub- task's you might need to check option Delayed execution in order to try the execution of the transition once the sub-task has completed its current transition.
Other examples of that function
- 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)