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

Parent link field on epic not showing initiative

Tarun.Talwar

Got the Jira premium version activated and created a top-level project where Initiatives are sitting. Now when trying to create/link Epic from another project and navigate to the Parent field, do not see the initiative appearing.

I do see 'Plans' tab on the top band to confirm the premium version but when navigate to Plans Settings, do not see any reference to advanced roadmap settings. Did Jira not call in Advance roadmap anymore, all I see is Timeline, a few videos online and documentation all refer to 'Roadmap'.

Accepted answers

John Funk

Hi Tarun,

First, yes it is now called Timeline and not Advanced Roadmap anymore. Same object, just different name.

Can you share some screenshots of your Hierarchy and the Epic screen with the Parent field? Are any issues showing in the Parent field? Are you typing the value of the key for the Initiative?

All comments

John Funk

Hi Tarun,

First, yes it is now called Timeline and not Advanced Roadmap anymore. Same object, just different name.

Can you share some screenshots of your Hierarchy and the Epic screen with the Parent field? Are any issues showing in the Parent field? Are you typing the value of the key for the Initiative?

Tarun.Talwar

Hey John, thanks for responding.

Have added the screenshots for reference. The strange thing is that I'm able to assign epic as a parent to initiative but not the other way around how I intend to. The issue hierarchy screen does not allow me to change the number or drag down the position Epic screen.png initiative screen.png issue hierarachy.png

John Funk

Right there is a bug in the system that won't allow you to drag those up and down. And you can't Add the initiative type at level 1 while also deleting Epic. What I have done in the past is to delete the Epic issue type first, but this was on a brand new instance. Then add the initiative to level 1, and then add Epic back and put it at level 2.

If you can't do that, you probably want to submit a support ticket to Atlassian to find out what to do. If you do that, please post back here with the resolution.

https://support.atlassian.com/contact/#/

Tarun.Talwar

Thanks again John, finally the issue is resolved, and I was able to get help from Atlassian support for the fix.

The issue was having the configuration of ‘Initiative’ rather than 'Top Level Initiative. All good now and working as expected.

There is also no need to change the numbered hierarchy.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

advanced-roadmaps