How do I create an automation that builds the hierarchy I want to display?

[Justin Robinson]

I am looking to create an automation that will start at the legend issue type and automatically build each issue type that should be below it in the issue type structure (initiative, epic, tasks, sub-tasks, etc.) and auto assign each parent task to each child task. For example: the automation will kick off after I create the Legend, it will build and create and initiative (and auto-assign the legend as its parent), it will create an Epic under that initiative and auto-assgn the Initiative as the Epics parent (an so-on and so forth)

Any advice? Or Suggestions? 
Thanks in advance

[Bill Sheboy]

Hi @Justin Robinson 

What problem are you trying to solve?  That is, why do this?  Knowing that may help the community to offer better suggestions.  Thanks!

Until we know that information...

Automation rules are able to create issues with relationships, including parent / child linking between issues.  This is a common scenario when a particular work item (e.g., New Hire Onboarding) has a set of standard child issues which are always created (e.g., Create Badge, Build Laptop, Scheduled Welcome Lunch, etc.).

However you are describing automatically creating five levels of issue types, starting with what appears to be a very high, conceptual level to a very low, implementation detail level.  I am trying to understand a scenario where that many levels would be pre-defined for any new request.  Perhaps the problem you describe will help clarify that perceived need.

Kind regards,
Bill

[Himanshi]

Hello @Justin Robinson , 

Welcome to the community!

You might be interested in a setup something like this : 

Trigger : Issue created 

If else condition: 

Issue Type equal to Initiative

Then add action : Create Issue : Summary 

Ensure to add Parent field equal to trigger issue 

Put Re-fetch outside the condition and then repeat same process for each hierarchy setup below. 

I ensured to select "Create complete hierarchy of Issue" from rule details. 

Only catch here is execution time and limit that affect your system performance and you are executing multiple automation that also functions issue creation at same time it would confuse the automation rule , same goes with manual creation of issue . Automation can get confused if there is manual issue creation of any hierarchy level at the same time. 

Here deliverability is my highest issue hierarchy: 

Please try and test it out. 

Additionally, you can also create issue using Webrequest that's up to you.

Hope it helps.

[Justin Robinson]

Thank you @Himanshi I am going to build out a test using this format and see what I am able to produce. Thank you for giving me some much needed insight to get started and moving in the right direction.