nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Add child issue option is not showing up - separate projects for initiatives, epics, and teams

Rob Horan

I was trying to set up a dedicated project for Initiatives, another for Epics, and multiple projects for individual teams. The goal was to have a dedicated Initiatives project that would have child epics from a dedicated Epics project, and then have child task-level issues from the team projects.

When I construct the projects this way I am unable to see the Add Child Issue option. I am able to build the structures using the parent field in the child tickets, but I have to create them first and then add the parent.

Is there a way to get the add child button to show and allow me to select the project I need to create child tickets in?

Accepted answers

Mohanraj Thangamuthu

Hello, Good day. For your requirement your current workaround is best option (to create the child issue and then add the parent field). To enable the add child issue option, you need to add the child issues types to the project where you have initiatives (I believe you want to have only initiative in this project)

All comments

Mohanraj Thangamuthu

Rob Horan

So there's no way to use add child to add child tickets in other projects?

Mohanraj Thangamuthu

Not until you add child issues types to the project where you have the parent issue. Or you can add the parent directly in child issue. Thanks

Rob Horan

Adding all the child types will defeat the purpose of having work broken out to team projects, with epics and above in their own separate Jira projects.

It would just be great to have the ability to add issues from within the epic itself. Yes, its possible to do so in plans, but that UI is not the friendliest, and then all changes need to be committed in a separate step,

Shah_ Piyush

I added validator to make "Parent" field mandatory when Parent lives in a different project space. This is not most convenient but that is the price to pay for having multiple project spaces.

I did file Atlassian enhancement req to allow adding a child from another project when you click on "+Add". And may be this can be restricted based projects are configured with same "category" as seen on project "Details" page. May be there are better ideas.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

advanced-roadmaps

epic

roadmap

initiative

tasklist

parent

child

portfolio-for-jira-cloud