Jira automation - create multiple issues complexity

Lynne Ratcliffe

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

Bill Sheboy

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