Can I create a hierarchy type structure and save it as a template?

[Elena-Alexandra Enache]

Hello everyone!

So, my need is the following: for every new project I need to create a structure like this: Task of type 1 -> attached a child task of type 2 -> attached a child task of type 3 -> attached tasks of type Task.

Can I automatically create this structure (different from the standard Hierarchy structure available in JIRA) and also save it as a template for future use?

It's fine if only JIRA admin can create the template as long as any other role can use it.

Thanks

[Luka Hummel - codefortynine]

Hi @Elena-Alexandra Enache

If you are willing to use a third-party app, our Deep Clone for Jira can clone whole issue hierarchies. With it, you can create your template hierarchy once and clone it often as you want. My colleague @Marlene Kegel - codefortynine even wrote an excellent community article about that use case.

You can clone a whole issue hierarchy the following way:

1. Navigate to the issue you want to clone

2. Click Action menu ••• > Deep Clone

3. Select Epic/Tree Clone

4. Configure and create your Epic/Tree Clone

[Trudy Claspill]

Hello @Elena-Alexandra Enache 

Jira does not support multiple issue hierarchy structures. There can be only one structure and it applies globally.

The default structure is

Epic
|-- standard issue level (i.e. Task, Story)
    |-- subtask issue level

If you have a Premium subscription the Jira Administrators can expand the hierarchy above Epic to add levels, but you can't add levels inside of the default structure.

Without a Premium subscription you cannot set up the 4 layer structure you described in a way that Jira will natively recognize the parent/child relationships you want to create.

You might be able to do so with a third party app, if your Jira Admins are willing to obtain such an app.

Your other choice is to use generic issue linking to create the relationships between the issues. Note that Jira will not treat those relationships as parent/child though.

As to creating a reusable template for this structure, it depends on the implementation path followed.

But let us back up a moment and ask - what problem are you actually trying to solve with the alternative hierarchy? Why does the default hierarchy not work for you?