Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,159
Community Members
 
Community Events
184
Community Groups

Trying to close parent when all sub-tasks and linked issue close

I'm using Jira Service Desk Cloud and Automation for Jira. I have a use case where when a "New Client Request" issue is created, it creates 2 sub-tasks and a "Setup software" issue. I want to close the "New Client Request" issue when the 2 sub-tasks and the "Setup software" issue are all closed.

In my research, I've found instructions on how to close parent issues when their sub-tasks are all closed and I've found instructions on how to close a linked issue when the issue it's linked to is closed. But I haven't seen anything that combines the 2. Is that because it's not possible or is it just something that hasn't occured to anyone else to try?

2 answers

1 accepted

0 votes
Answer accepted
Z B
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Dec 14, 2019 • edited

Hi, it seems I have managed to find a solution, attached the screenshot of the automation rule in 2 parts. I tried and it worked for me, please try to customize the issue types, link types, try it, and let me know if it works for you or still some changes are needed.

1.png2.PNG

@Z B Thanks so much! It worked great!

Like Z B likes this

@Z B Actually, I just discovered a problem. I just realized that the use case I mentioned was slightly wrong. I was so excited to get it to work that I forgot a slight detail.

When a "New Client Request" issue is created, it can create 2 sub-tasks and a "Setup software" issue. It can also create 1 sub-task and a "Setup software" issue. Or just create 2 sub-tasks. It depends on what checkboxes the Reporter chooses in the customer portal. So the solution you found works, as long as their is always a sub-task and a "Setup software" issue. But since it is possible that the customer won't want us to "Setup software", I need the rule to be flexible enough to be able to close the main issue no matter what the situation.

Do you think it's still possible given this new wrinkle?

Like Z B likes this
Z B
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Dec 17, 2019

So now it closes IF there are at least 1 Closed Sub-tasks AND 1 Closed "Setup software" issue.

And basically you want to close the "New Client Request" automatically also IF there is only 1 Closed Sub-tasks OR 1 Closed "Setup software" issue.

I created 1 separate automation for that and the 2 seem to match. Create this in the same project, turn on both. I did some testing and it worked for me but you should test it too.

3.PNG4.PNG

HI @Z B i'm struggling to get the second part due to it being a separate screen shot. where in the tree should it start? Can you reduce size so you can get everything on 1 page? Thanks in advance.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events