Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Transitioning parent ticket when sub tasks are all completed

Jenni Davison
Contributor
July 6, 2023

Hey all, 

I have an automation issue - I have a task, which when created has 5 subtasks. For the subtasks to be completed they must have a status of 'Approved' or 'not required'

I would like a rule that says when all 5 of these subtasks are either 'approved' or 'not required' the parent Task moved to complete.

This is the automation I have at the moment, but doesn't wait for all subtasks to be a completed status before transitioning.

Can anyone see what I'm doing wrong please?

jira help needed.JPG


 

4 answers

3 votes
Mikael Sandberg
Community Champion
July 6, 2023

Hi @Jenni Davison,

Welcome to Atlassian Community!

The reason the parent is not waiting for all sub tasks to be done is because you are not checking for it in the parent branch. If you go to Automation > Templates you will find a rule called "When all sub-tasks are done → move parent to done" and as you can see it includes a condition in the parent branch that checks that all sub tasks have reached done status.

Screenshot 2023-07-06 at 1.41.09 PM.png

1 vote
Laurie Sciutti
Community Champion
July 6, 2023

Hi @Jenni Davison ~ I do something similar. 

1.  Confirm that transitioning the Parent (Task) to "Approved" is the correct status for that workflow (and not part of the sub-task workflow). 

2.  Also, if you have any workflow in place that disallows a parent from being closed while it still has open sub-tasks, you'll need to add a condition to ensure no other related sub-tasks are open:  I use the related condition shown below.

 

HTH

image.pngimage.png

0 votes
Jenni Davison
Contributor
July 7, 2023

Thanks everyone - really helpful.  Much appreciated

0 votes
Trudy Claspill
Community Champion
July 6, 2023

The other answers have addressed your specific issue.

I wanted to add that there is a Library of prebuilt Automation Rules and the use case you have is one of those prebuilt rules.

You would need to adjust the rule for the specific Status values in your configuration, but the structure is there.

Screen Shot 2023-07-06 at 3.02.41 PM.pngScreen Shot 2023-07-06 at 3.03.21 PM.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events