Futures used to implement the example
Example: Change parent's status depending on sub-task's summary (Transition issues)
In this example the parent issue should be moved to status "Estimate created" when the sub-task's summary contains "create estiamte".
This can be done with post function Transition issues and implementing it at "Create issue" in the subtask's workflow:
Text to be parsed: %{00000} ~ "create estimate"
Note that:
- %{00000} is field code for field "Summary"
Once configured, the transition will look like this:
BITTE DIE MAKROS UM NAME DER POST FUNCTION (LINKES MAKRO) UND WEITERE LABELS (RECHTES MAKRO) ERGÄNZEN UND HIER DIE SECTION LÖSCHEN!
HIER DIE SEITE DANN BITTE AUCH UM JEWEILIGE LÄBELS ERWEITEN!
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)