JIRA automation to create sub-tasks based on components on a parent EPIC

[JIRAUser209]

Hello - 

I need help with creating a JIRA automation for creating sub-tasks based on the number of components on a parent epic. dont have a JIRA cloud instance. 

[Trudy Claspill]

Hello @JIRAUser209 

Welcome to the Atlassian community.

Are you trying to create child issues under the Epic based on the Components specified in the Epic?

When do you want that to happen? 

• When the Epic is created?
• When the Components field in the Epic changes?

Is the creation of the new issues based solely on the number of values in the Components field of the Epic?

How does the number of Components relate to the new issues to be created? Should the number of issues created equal the number of Components set for the Epic?

What information do you want to add to the new issues? Will the information be identical for each of the new issues?

[JIRAUser209]

Thank you @Trudy Claspill for the welcome :) 

- Child issues should be created when components are added to the Epic. We are using components to indicate the dev teams that will work on that epic. so want to create sub-tasks for them that can be used to track effort/time. 

- Yes, creation of the new issues is based on how many components are added to the Epic. so 1:1 component on epic to sub-task created. 

- I would like the component name to get auto-added to the sub-task component field as well. 

Do you have any suggestions on how to do this ?

[Trudy Claspill]

Sub-tasks are not typically made children directly of Epic issue types. Is "Sub-task" the type of issue that you want to create, or would you be specifying another issue type?

Will all the information in the newly created issues be identical except for the Component value?

I'm not sure that this can actually be done in a Jira Data Center environment. I am more familiar with Automation Rules in Jira Cloud, and there are some features available in Cloud that are not available in Data Center.

What version of Jira Data Center are you using?