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

Question on Issue Type Hierarchy, Issue linking, Plans, Roadmap

Matt Houck_65e3n8

I think the solution to my question is to set the Issue Type Hierarchy but due to the message "Moving or changing hierarchy levels of issue types will break existing parent links in all company-managed projects in your site. This change can't be reversed." I'm concerned that I may break the linking within other projects in our instance of Jira which I need to avoid if at all possible. The parent / child relationships in the other projects are only subtasks to issues.

My goal is to properly account for the following hierarchy in my project while reviewing the plans and Roadmap with: CIT (top level in my project), Resolution Plan, Milestone, Sub-Task. So, in the plan hierarchy view I want to be able to have a CIT with child resolution plan issues as dependencies, which will have Milestone issues as dependencies to those.

Currently the hierarchy is set: 2 Resolution Plan, 1 Epic, Story, Sub-Task. Note, Story and Sub-task do not have hierarchy numbers by them.

My Questions:

1. If I modify the hierarchy will parent child relationships in other projects break if I use the final hierarchy as: 1 Epic, 2 CIT, 3 Resolution Plan, 4 Milestone, Story, Sub-Task?

2. If it will break the parent / child relationships in the other project is there another way to accomplish my goal?

Accepted answers

Ste Wright

Hi @Matt Houck

I'm a little confused on the need, but I've assumed from the question you want to:

Move Epic to the top (above CIT)
Your hierarchy is CIT > Resolution Plan > Milestone > Story > Sub-task
The rest of the platform still needs the current hierarchy

---

The bottom 3 levels (Epic, All Other Standard Issue Types, All Sub-task Issue Types) are locked in place - so it's not possible to move the Epic to the top.

But, you could still achieve what you need:

Place CIT at the top of the hierarchy (#3)
Place Milestone at the same level as Epic (#1)

^ This should have zero impact on the rest of the hierarchy - as you've added a layer which wasn't there previously, and not modified any of the current layers.

---

A few notes on this approach:

Whilst this won't modify the data, other Projects will see another layer appear in their Advanced Roadmaps Plans that they'll need to filter out
If the Parent Link is on the "Resolution Plan" screen for other Projects, they'll be able to set "CIT" Issues as the parent
You'll need the Parent Link on the Story screen, to set a Milestone as a parent
Stories will not be able to have both a Parent Link and an Epic Link concurrently
Milestone won't have the same functionality as Epic - eg. the Epic Panel in boards

---

I'd still test this of course, in your Sandbox, but the above should work.

Let us know how it goes

Ste

All comments

Ste Wright

Hi @Matt Houck

I'm a little confused on the need, but I've assumed from the question you want to:

Move Epic to the top (above CIT)
Your hierarchy is CIT > Resolution Plan > Milestone > Story > Sub-task
The rest of the platform still needs the current hierarchy

---

The bottom 3 levels (Epic, All Other Standard Issue Types, All Sub-task Issue Types) are locked in place - so it's not possible to move the Epic to the top.

But, you could still achieve what you need:

Place CIT at the top of the hierarchy (#3)
Place Milestone at the same level as Epic (#1)

^ This should have zero impact on the rest of the hierarchy - as you've added a layer which wasn't there previously, and not modified any of the current layers.

---

A few notes on this approach:

Whilst this won't modify the data, other Projects will see another layer appear in their Advanced Roadmaps Plans that they'll need to filter out
If the Parent Link is on the "Resolution Plan" screen for other Projects, they'll be able to set "CIT" Issues as the parent
You'll need the Parent Link on the Story screen, to set a Milestone as a parent
Stories will not be able to have both a Parent Link and an Epic Link concurrently
Milestone won't have the same functionality as Epic - eg. the Epic Panel in boards

---

I'd still test this of course, in your Sandbox, but the above should work.

Let us know how it goes

Ste

Matt Houck_65e3n8

Thank you so much for responding and reading through my gibberish!

I think what I am reading is that I can add new levels of hierarchy without causing linking to break. Is this true?

The effect may be that additional levels may show up in roadmaps that may need to be filtered out of projects that do not use the levels I create.

You mention sandbox. This is interesting as I am not aware of the sandbox so I will look into this more. This might be exactly the thing I need to test this out!

Ste Wright

Hi @Matt Houck

Yes - the hierarchy should not break if you are adding...

A hierarchical layer above the existing hierarchy (i.e CIT)
Additional Issue Types into existing layers, but not removing any (i.e Milestone)

^ Of course, there are circumstances where you could break it - for example, adding a layer inbetween two existing layers, or removing Issue Types from existing layers - but neither of those examples seem relevant to your requirements!

I would still encourage testing it in your Sandbox first though. Sandboxes are available to you if you have a Jira Premium or Jira Enterprise licence. Check out more on this page - Manage product sandboxes.

Ste

Matt Houck_65e3n8

Thank you for the responses! I had some vacation time I was using last week but will work on it this week and if everything goes as expected I'll accept the answer! Thanks again for bearing with me!

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