Impact to running projects by adding hierarchy levels
Asked by Kevin Cocco:

Hi Everyone,  

I'm considering to upgrade plan and use the advanced roadmaps, requiring the ability to configure new hierarchy levels.  

Since adding new hierarchy levels applies to all organization projects, i'm still hesitating. We have running projects that should not be influenced by new hierarchy levels, but only for the advanced roadmaps.   

Do you know what exactly will happen to my current scrum/kanban projects if i add new hierarchy levels?  

Thanks in advance!

Best,

Kevin


Answers:
author: Daniel Capizzi
body: Hi [@Kevin Cocco](/t5/user/viewprofilepage/user-id/5259533) - on top of all the good advice that [@Fabian Lim](/t5/user/viewprofilepage/user-id/3131564) has already given, I also wanted to point out that you'll be asked to confirm before making any changes to your hierarchy that will break parent/child relationships.

I've attached a screenshot below of the pop up which will let you know how many issues will be affected and give you a link to see a selection of those issues. If the changes you've made won't break anything then they'll be applied straight away without showing the pop up.

![Screenshot 2024-01-19 at 11.01.56.png](https://community.atlassian.com/t5/image/serverpage/image-id/301378iA0C173ECBCB00C2B/image-size/large?v=v2&px=999 "Screenshot 2024-01-19 at 11.01.56.png")

Hope this gives you a bit more confidence to continue trying things with your hierarchy knowing you won't accidentally break anything without being warned first!

Cheers,

Daniel


author: Fabian Lim
body: Hi [@Kevin Cocco](/t5/user/viewprofilepage/user-id/5259533)

For your boards there will be no impact. Now you have to be careful with the fields you had populated for parent/child tickets. If you have a Feature as a parent of an Epic, and now you change the hierarchy things may break. For Epics and other issue types if you were using Epic Link you should be ok, but if you had parent/child relationships you will have to double check..

Regards,

Fabian

comments: author: Kevin Cocco
body: Hi [@Fabian Lim](/t5/user/viewprofilepage/user-id/3131564)

Got you, thank you very much.

We've been using the following issue scheme and hierarchy.

![Bildschirmfoto 2024-01-13 um 06.59.44.png](https://community.atlassian.com/t5/image/serverpage/image-id/300413iFCA3BF02683813E1/image-size/large?v=v2&px=999 "Bildschirmfoto 2024-01-13 um 06.59.44.png")

![Bildschirmfoto 2024-01-13 um 06.58.42.png](https://community.atlassian.com/t5/image/serverpage/image-id/300412iDE4B92AC2C73F0BB/image-size/large?v=v2&px=999 "Bildschirmfoto 2024-01-13 um 06.58.42.png")

So let's say our Epics are connected with Story's as parent relation and Story's/Tasks do have Sub-Tasks, do i need to worry about breaking any of those relations by adding a new Hierarchy level on top of Epics?

Thanks again!

Best,

Kevin


author: Kevin Cocco
body: That example might be more helpful![Bildschirmfoto 2024-01-13 um 07.17.00.png](https://community.atlassian.com/t5/image/serverpage/image-id/300414iDEFF62E5707C31CC/image-size/large?v=v2&px=999 "Bildschirmfoto 2024-01-13 um 07.17.00.png")

Epic CYR-8 -\> is top level hierarchy  
Story CYR-9 -\> is child issue of Epic CYR-8  
Sub-Task CYR-10 -\> is child issue of Story CYR-9  

now i want to add a hierarchy level (initiatives) on top of Epics and make Epic CYR-8 a child issue of initiative. would that now change anything in my boards?


author: Fabian Lim
body: In your scenario above, it should be ok. Since Initiatives are the top in the hierarchy. You just have to ensure that you communicate this to your company just in case they want to use initiatives at other levels. But your boards should not be affected.

Worst case scenario, you just revert the change .


Tags: advanced-roadmaps

cloud

hierarchy