On this page
Futures used to implement the example
Example: Moving story to "Ready for QA" once all its sub-tasks are in "Ready for QA" status (Transition issues)
When all sub-tasks of a story are moved to "Ready for QA", the story should move from "In Progress" to "Ready for QA".
Insert Transition issues post-function into transition from "In Progress" to "Ready for QA" in sub-task's workflow:
Text to be parsed is: count(siblingSubtasks()) = count(filterByStatus(siblingSubtasks(), "Ready for QA"))
That boolean expression checks that all the sub-tasks are already at "Ready for QA" status. It is also possible to check the sub-tasks against more status, e.g. "QA Accepted" and "Done". In this case the following expression can be used:
count(siblingSubtasks()) = count(filterByStatus(siblingSubtasks(), "Ready for QA, QA Accepted, Done"))
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)
