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; } } }

can I create an epic as a "child issue" of initiatives directly?

Hancheng Lvsiqing

hello team,

I'd like to create an epic as a "child issue" of initiatives directly, just like "create subtask", but it seems that I can't do it ?

background:

1. "initiatives" level added

2. field "parent link" available for epic issue

appreciate for your support.

Comments

Fabio Racobaldo [Catworkx]

HI @Hancheng Lvsiqing and welcome,

Epic is a standard issue type and not a subtask so the answer is no. My suggestion is to create an epic and link it to the initiative through a link.

Hope this helps,

Fabio

Hancheng Lvsiqing

hi @Fabio Racobaldo _Catworkx_ , thanks for your suggestion ! I know that epic is not a "subtask", can I "create epic" in initiatives?

Hancheng Lvsiqing

or "add a child issue" in initiatives, and this child issue is an epic?

Fabio Racobaldo [Catworkx]

There is not a specific button "Create Epic" that you can setup within initiative issue type.

jeremyn_e0bq0q

This is such a failure of design and deployment on Atlassian's part. They've done a lot to make Advanced Roadmaps (ne Plans) so valuable, yet leave out the ability to add children to the TICES issue typs above Epics, thus depriving users of an intuitive way to do what they've always done for their "container" issues (ie epics up until now).

We want to deploy Advance Roadmaps company wide, but when the project leads hate the way the new fields can't be used the same way as before it really makes life a lot harder on those of us tasked with deploying corporate wide changes.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

advanced-roadmaps