Forums

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

Jira automation - create multiple issues complexity

Lynne Ratcliffe
Contributor
March 24, 2022 edited

Hi all, hoping someone may be able to help. We are creating an automation that will create 6 epics and circa 29 stories for a specific team that has repeating work for each  initiative .

I know what I need to do as I have done it on a smaller scale. However, this is going to be quite large and there is no way to differentiate between each component and therefore if we have to go back and make a change, it’s not easy to find the correct create component. Is there some sort of setting (or something else) that will make if clear at a quick glance which component is which?

many thanks 

Lynne

1 answer

1 accepted

0 votes
Answer accepted
Bill Sheboy
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.
March 24, 2022

Hi @Lynne Ratcliffe 

If at all possible, I respectfully suggest you divide-and-conquer on this rule.  Automation has a 60 component limit (i.e. total of the trigger, branches, actions, and conditions) and so this rule will run right up against that limit.

Perhaps consider one rule to create the 6 epics and have separate rules to create the child issues, triggered by the creation of each specific epic (if they can be distinguished).  When using this method, the secondary rules should enable the "Allow Rule Trigger" option in the details section.

And with this approach the rules will run faster due to the asynchronous processing of each rule.  

To your question about differentiating the components in longer rules, there is nothing built-in to help with that.  Once you split rules, it may be easier to see what is happening.  And if not, perhaps throw in some Audit Log actions to make the rule sections more visible.

Kind regards,
Bill

Lynne Ratcliffe
Contributor
March 24, 2022

Thanks Bill, if it’s not too much to ask, can you give a little more detail as to how I might make this work?

The trigger is the creation of a theme issuetype and we use the project code put in the theme summary as the prefix for the summary for all tickets to be created.

Lynne Ratcliffe
Contributor
March 24, 2022 edited

Or, could I just create 6 rules, 1 for each epic & related stories, all triggered by the theme creation?

Lynne Ratcliffe
Contributor
March 25, 2022 edited

So I have tried creating the 6 rules as per my last comment, it does work but the epics aren't created in the order they should be.

I'd like to test your suggestion and create the epics first, but i'm not sure on how to trigger the children for each Epic.

Lynne Ratcliffe
Contributor
March 25, 2022

@Bill Sheboy thanks for your tip. After playing around a little i got this to work.

Like • Bill Sheboy likes this
Bill Sheboy
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.
March 25, 2022

Awesome!  I am glad you got it to work.

Suggest an answer

Log in or Sign up to answer