Can I add "Add Child" button to a Issue type in a non-epic "hierarchy"?

[Scott Buratt]

In a Company Managed project, I created a hierarchy from the Issue Type Hierarchy configuration as follows

• Level 0, above
• Level 1, above
• Level 2

and am looking to be able to create Level 1 as a child to Level 0 and create Level 2 as a child to Level 1 using the "Add a Child" button.

As currently there's no obvious way of adding the "Add a Child" button, I have to go to the particular "Level" tickets and manually add the "Parent Link", which then shows up as a Child in the "Level above"

How do I add the "Add Child" button to the Level 0 and Level 1 issue types?

Thanks

[padraik · Accepted solution]

I *really* hope someone knows how to do this.  I've had more than one client ask for it and I haven't been able to deliver.

BUT - since I'm used to this question, I do have a canned response ready for you.  "Use the Plans view"

Go to the lucky ticket who's about to have children, and click the three-dot menu.  Select the child issue type, and type the summary of the new issue into the text box that opens for you.

In my example image here, "level 0 ticket" is my parent (type is product initiative) , and in the three-dot menu, "Create epic" would say something different for you, but select the level 1 issue type you want.

-------------------------

It will be "created" as a child, populating the "Parent link" field appropriately.

-------------------------

Don't forget to Review changes (button in the top right)

-------------------------

And to save them in Jira - without this step, nothing will update in your project.

[Scott Buratt]

Thanks @padraik 

That suffices for now and greatly appreciated

I did notice that the "create child" chose list seemed backwards but that's probably some misconfiguration on my part where

- Having my "Level 0" then wanted to create a "Level 1" child only worked correctly if I selected "Create Level 2"

- Then, creating a child under "Level 1" only worked correctly if I selected "Create Level 0".

Either way, for now, while a bit awkward, you've provided a solution.

Now, if Atlassian can enable or tell us how to add the "Add Child" button to issue types that support children but aren't Epics or Tasks, life would make more sense :)

[padraik]

Glad I could provide *some* help.

Hopefully someone has the real answer, this would be great to have.

[Nick de Palézieux]

I'm also looking for this functionality.

Since in the issue hierarchy configuration, I can only add new levels above epic, I'm forced to create my own epic type that I can place at the top, creating the following hierarchy:

- My custom Epic

    - Change proposal

        - Implementation

In the advanced roadmaps view, I can create child issues for each of these, but the Jira users in my team just look at the issues themselves, so they want to add children from the issue view.

[Angel Osberg]

I'm also looking for this functionality as our Jira users also want to just be able to create child issues from the issue view as well. Rather than being in Jira on the issue, then navigating to advanced roadmaps to then be able to create from the parent issue. 

[Jesse Gray]

Having to either work "child up" or creating from the roadmap is a poor work-around to the "single epic jira vs multiple epic roadmap" problem.  Jira clearly can handle the parent relationship, so now the QOL tools like this just need to happen.  The hard part is done.  Do this: https://jira.atlassian.com/browse/JSWCLOUD-17573

[Karen Aiken]

There is a closed feature request for this - can we lobby to reopen?

https://jira.atlassian.com/browse/JSWCLOUD-17573

[Hannes Krug]

There is another related ticket here still open and currently gathering feedback: https://jira.atlassian.com/browse/JRASERVER-68805

[Karen Aiken]

Thanks @Hannes Krug - adding my vote and notes there.

[Karen Aiken]

I'd also like to see this functionality - on the issue view page itself.

We're using a Platform Epic (parent of Epic in the hierarchy) to gather Epics together, and then pointing people to the Platform Epic for a quick, overall, summary view of the work that's going on. We attach any needed links and documentation to that top-level issue, so it's a powerful starting point.

If we have to navigate away to the (ever-growing) Roadmap, we have to find that Platform Epic in the hierarchy (it's 3rd level in our hierarchy) in order to add the children. Quite a few extra clicks.

Take care,

Karen

[Hannes Krug]

Searching that option too