Tree of tasks - How can I do it?

[DLeo]

Hello everyone,

I'm new to the forum, so please do correct me if I did something wrong.

I would love to create a fixed tree of tasks that I can insert in my board as a "Story" (or whatever).

What I'm doing right now is creating a story that has tasks under it and then sub-tasks under each task.
Even this way though, I find myself manually re-creating the whole structure every time.

Is there a smart way of doing this that I don't know?

Thanks in advance.

[Trudy Claspill · Accepted solution]

Hello @DLeo 

Welcome to the Atlassian community.

Are you working with a Company Managed project or a Team Managed project?

Can you share with us screen image examples of a Story under which you have created Tasks and a Task under which there are subtasks?

I ask because the native Jira issue hierarchy does not allow a Task to be a child of a Story. The native hierarchy has three levels:

Epics
|-- standard level issues (Story, Task, Bug, etc.)
    |-- subtask level issues

Jira does not allow issue types from the same level to be "children" of each other.

There are a few ways that you might automate this task.

You could use Automation for Jira to create the issues for you.

The built in Clone operation available from an issue will allow you to clone that issue and its subtasks.

There are third party apps that provide more sophisticated issue cloning functionality.

https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=clone

There are also third party apps that enable you to create a template of issues that you can use to create a set of issues.

https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=issue%20template

[DLeo]

Thanks for the quick and exhaustive answer,

yes, my bad; I did an "Epic", then "tasks" and then "sub-tasks".

This brings another question: can I clone an "epic"? This would mostly get me to what I'm trying to achieve.

Thanks again.

DL

[Trudy Claspill]

When the native Clone operation is used for an Epic only the Epic itself is cloned. The operation doesn't include the Epic's child issues nor their subtasks.

You could still accomplish the cloning with Automation for Jira, or third party apps.

[DLeo]

I've created an Automation to auto create the sub-tasks I need upon creating tasks with key-words in the summary.

So procedure is:
- creating a Epic with the name of the project for which we need to do the work;
- creating 3 tasks with the key-words;

- sub-task will be created by the automation;

I'd say good enough.

I tried to make a rule for when the Epic gets created but couldn't make it work.

Thanks again!

[Trudy Claspill]

Hello @DLeo 

If you would like some help with the rule you created for to apply to when an Epic gets created, please post a copy of it here, post the information from the Audit Log for that rule's execution, and tell us how it was not doing what you wanted.

[Danut M _StonikByte_]

Hi @DLeo ,

Our Great Gadgets plugin could be helpful here. It offers a Work Breakdown Structure (WBS) gadget that takes the issues from a specified filter and displays them in a tree structure, by their hierarchy, in form of Epics > Stories, Tasks > Sub-tasks, exactly as you want.

All you have to do it to have a filter that returns the issues to be grouped and to configure the gadget to use this filter. Then, the magic will happen.   

Please note that this app offers many other gadgets that you will find useful. Just have a look over the articles from our blog to make an idea. It can be a great asset for your team and company.

I hope this helps. 

Thank you,

Danut