How to Setup and Link Multiple Hierarchies

[Jespir Ragbotra]

Hi - I need help understanding how to create multiple hierarchies beyond just the Initiative one that's mentioned here in the help article: https://confluence.atlassian.com/advancedroadmapsserver0329/configuring-initiatives-and-other-hierarchy-levels-1021218664.html#:~:text=Go%20to%20application%20settings%2C%20click,Click%20Save%20changes.. 

Our organization has 5 different hierarchy levels that all need to link together somehow so we see it in advanced roadmaps:

1. Enterprise Objectives

2. Enterprise Strategies

3. Enterprise Themes

4. Enterprise Initiatives

5. Epics

From what I understand, each hierarchy (besides the Epics) can be configured to have their own Project and their Issue types.

In this case I created a separate project for hierarchy level 1-4, and then I added Issue Types to correspond with each of those.

After that I actually added the issues with the name of objectives, strategies, etc to populate some test data. 

After that I even configured the hierarchy to match that exact structure: 

Yet, I'm unable to link them correctly to each other via the Parent Link (the only time this field populates is when I create an Epic). 

Here you can see that I am trying to create an Enterprise Strategy Issue Type. When I click the parent link it says "no matches" when I would like to be able to select issues from the hierarchy above it which would be Enterprise Objectives: 

What am I doing wrong here? And is there an easier way to setup multiple hierarchies that will link to multiple projects? (note: the Epics will live in a separate project where we have boards for our engineering teams. This work needs to role up to all the hierarchies listed above). 

[Trudy Claspill]

Hello @Jespir Ragbotra 

Have you created issues of the type at that parent level?

If you are creating an Enterprise Strategies Issue Type, then in the Parent Link field you should be able to type in the Issue Key for an issue of type Enterprise Objectives.

If you are creating a Story issue type, then you would need to modify the Epic Link field to identify the Story's parent Epic. You would not use the Parent Link field for linking Stories to Epics.

Also, I believe that you are looking at the documentation for Advanced Roadmaps on Jira Data Center. This is the link for configuring the issue hierarchy in Advanced Roadmaps for Jira Cloud.

https://support.atlassian.com/jira-software-cloud/docs/configure-custom-hierarchy-levels-in-advanced-roadmaps/

I have not compared the documents in detail to look for differences.

And this is the home page for all the Advanced Roadmaps documentation for Jira Cloud.

https://support.atlassian.com/jira-software-cloud/docs/plan-and-view-cross-project-work-with-advanced-roadmaps/

[Jespir Ragbotra]

What do you mean at created issues at the "parent level?" If you mean did I create an issue with the type as "Enterprise Objectives" then yes I did do that. However, only at the Epic level is it allowing me to add an "objective" as the parent link. 

When I go to create an issue of "Enterprise Strategy" - that's when I actually want to see the parent level "objective" issue I created under the "Parent Link." Let me know if that makes sense! But I have followed all steps according to the article you linked! And I also made so to create issues at the top parent level before attempting to create issues at the second level. 

[Jespir Ragbotra]

Happy to send a video if that's easier! Thanks for trying to help!

[Trudy Claspill]

Yes, you got what I meant about creating an issue at the parent level. I phrased that poorly, but you figured it out. :-)

When you are creating an Enterprise Strategy issue, what happens if you type into the Parent Link field the issue key for the Enterprise Objectives issue you created previously? And then save the Enterprise Strategy issue?

[Jespir Ragbotra]

Thanks! It says "no matches" - I added a screenshot above as well.

However, if I create an Epic issue type, it does shows the Enterprise Objective. That's what's confusing because based on how I setup the hierarchy, it should offer the Objective issue at the Strategy level not at the Epic level. 

Maybe it's an issue with my Issue Type Scheme? Here's how I have it: 

[Chrissy Clements]

Hey Jespir,

Once you have the issue types and the hierarchy set, you can add this parent/child relationship via advanced roadmaps.

Try this docco: https://support.atlassian.com/jira-software-cloud/docs/configure-custom-hierarchy-levels-in-advanced-roadmaps/

[Jespir Ragbotra]

Hi Chrissy - thanks for the response. If you take a look at my post, you can see that I have set up the hierarchy as according to the article (I included a screenshot as well). But the issue is that the Parent Link doesn't work at the issue level when I need to start linking the hierarchy issues together. 

[Chrissy Clements]

It won't.  You can only create that parent link from within the advanced roadmap view.

[Jespir Ragbotra]

thanks Chrissy - can you explain what you mean by that?