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,502
Community Members
 
Community Events
184
Community Groups

How to automatically create subtasks triggered by multiple components?

Hello - I would like an option to trigger the automatic creation of subtasks if there are multiple components in an Issue / Story. I see some other conditional logic to choose from on the component field, but not a count condition for more than 1..

It would be very good if each subtask could include the name of the component also as a nice to have. 

 

Anyone know if there is a way of setting this up? 

 

Thanks!

1 answer

1 accepted

0 votes
Answer accepted
Michel Neeser
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.
May 18, 2023

Hello @Miriam Callahan and welcome!

I am not sure what your exact use case is, but I think you could achieve your goal with the following automation rule:

Automation_-_Jira.png

Automation_-_Jira-2.pngAutomation_-_Jira-3.pngAutomation_-_Jira-4.png

 

This rule gets triggered if a new component has been added to an issue. Then, it checks if there is more than one component set on the issue. If so, it creates a new sub-task for every component assigned, where the name of the sub-task is the name of the component.

Hope this helps!

Hi Michel,

Thanks so much I have lots to try out here... Appreciate this quick response!

Just a question on the above,, If Someone were to set up an Issue or Story with multiple components initially would the subtasks be created from that first creation?

As opposed to the Issue / Story being set up with one component  originally and then once a new component is added the rule being triggered...

I definitely have plenty to work with in your response so thanks again for that! :)

Michel Neeser
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.
May 18, 2023

@Miriam Callahan

If Someone were to set up an Issue or Story with multiple components initially would the subtasks be created from that first creation?

Yes, because the trigger "Value changes for" fires for newly created issues as well.

Thanks very much again appreciate that!! 

Michel Neeser
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.
May 19, 2023

@Miriam Callahan If it works, please consider accepting the answer, maybe it is helpful for others as well. Thank you!

Thank you again Michel this really helped! I just accepted your answer there! :)

Suggest an answer

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

Atlassian Community Events