Using Automation for JIRA is it possible to transition the parent when all subtasks are resolved?
This is definitely possible using the related issues action and condition:
Lets break this rule down:
Hey Andreas,
Just expanding on this a little bit... I use multiple different subtask types. Is this powerful enough to differentiate? i.e. I can pick the subtask type I want to compare and then trigger a parent transition (and or do this via a filter searching for those subtaskIssueTypes())?
If so, that's incredibly powerful for me!
Hey Russ,
Yes you can certainly do more filtering. We don't support else statements yet, so right now you'd have to setup multiple rules.
In the rule shown above you'd simply insert another condition before the "Then: For Parent" action. You could use a JQL condition for example to test "type = myspecialsubtasktype" (or any JQL really). If the sub-task that was transitioned matches then the rule will continue and transition the parent. If it doesn't then rule execution will stop.
You can also add more conditions in the "Then: For Parent" branch to for example only transition the parent if it is of a specific type/JQL match.
Setting up multiple rules is simple - you can just got to 'Create rule' -> 'Copy rule' to copy an existing rule if you just want to change the condition. We'll add proper 'else' support in future but for now this should work as well.
If you can describe a more specific example I'm happy to provide an example rule as well.
Cheers,
Andreas
Thank you for the reply, it's massively useful. Here is a full on use case:
1) I have multiple subtasks (i.e. Dev Task, Test Task, Documentation)
2) Each has it's own workflow
3) Parent's have their own workflow
Use Case:
Update Parent from Waiting for Dev to In Dev when any Dev Task is not new
Current thought: One automation rule that says Transition Parent to In Dev when JQL filter says dev tasks status is not new
Update parent to waiting for test when dev tasks are closed
Current though: another rule that says transition parent to Waiting for Test when JQL filter says all dev tasks closed
I guess the bit I find a little tricky right now is iterating over multiple subtasks to say 'all in status' .. but it looks like there's a rule in the compare bit that does this.. Could you help clarify this for multiple different task types? Just multiple rules?
Hi all,
I am struggling in automating to automatically close the parent if all linked issues via link type "Forwarded" are Resolved.
I've already tried with JMWE and Automation for jira but unfortunately without results...
Have somebody experience with that?
Any idea will be welcome
Thanks
Kind regards
Hi Guys,
I am trying to achieve the same thing in question with no success. Attached is the rule, I am not sure if I am doing it wrong because from the first screenshot which andreas posted, mine doesnt look same
1. I could not find compare 2 values option but mine just says match 2 option
2. It doesnt let me add a new action of the parent at the same root after I used if statement
I am not sure if anything has changed with regard to the version I am using.
Please advise.
Please ignore my earlier message, I was able to figureout what was wrong. Its my mistake . This raises another question for me is that
Can we include multiple subtasks inthe "Second value" option of the if condition?
My end goal is, when someone creates a issue and transition to a 1st status, it needs to create multiple subtasks, and when all the subtasks are complete it should move to next status where another bunch of new tasks are created and when subtasks are closed again move to next status and so on.
I was successful in using automation for this and tested with one subtasks at one transition using this, but I would hate to create multiple conditions. I could use special string for all sub tasks and use contain option in if compare.
Just wanting to know what the best recommended approach/solution to achieve this.
Using Subtask (Test Executions) for Parent Use Test Cases
Automation seems to work and I receive notification but parent status isn't updated as soon as all subtasks are Passed.. seems to be a delay. I need to either refresh screen or exit to see the parent Use Test Case status updated to Passed.
Using this rule because testers forget to update parent when all tests are passed
It looks like you're new here. Sign in or register to get started.
