Add an Extra Hierarchy level (Impact)

Nuno Pimenta _ADM_ July 31, 2023

Hi All, 

Currently in my organisation there are 4 Hierarchy levels 

#2 - Initiative
#1 - Epic
Story - All standard issues
Sub Task - All subtasks

 

i create a brand new issue type, and i would like to place it on #3

Before save i was prompt with the warning message

"Number of affected issues: 202  (view sample)"

I would like to understand what is the real impact on this issues, if someone can give me a heads up will be appreciated.

 

thank you in advance!

2 answers

1 accepted

0 votes
Answer accepted
Dave Mathijs
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 31, 2023

Hi @Nuno Pimenta _ADM_ 

Issue types which now have issue links between any of the current hierarchy issue types may be broken when you add a new issue type to the issue type hierarchy.

Please check for any Impact issue type and its issue links.

Additional question: Why would you consider an issue type called Impact as a level above Initiative? This is a strange way of naming your issue type in my opinion.

Are you using Advanced Roadmaps to create parent/child relationships between to issue levels?

Nuno Pimenta _ADM_ July 31, 2023

Hi Dave! 

Thanks for the answer!


the new issue type is called "Objective" not Impact :)

This is a request from one of the Project Leads in the organisation that would like to have the Hierarchy Objective -> Initiative -> Epic -> StandardIssueTypes() in a new project.

While looking to it i realise the change affect other issues in the site, so would like to understand what is the impact in the affected issues.

Dave Mathijs
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 31, 2023

Okay, Objective seems more reasonable. 🙂

Since you are on a Premium Plan, do you have a Sandbox installed? There, you can test the impact.

If it's a request from ONE of your Project Leads, have you considered the impact for the entire Organization? Have you communicated this important change to ALL of the Project Leads?

See the official documentation article here: Configure the issue type hierarchy 

 

Changing your issue type hierarchy will break existing parent and child relationships between your issues.

When you attempt to modify the existing structure of your issue type hierarchy, Jira will calculate the impact of these changes and require confirmation to proceed.

Please ensure that you understand the risks and impact of changing your issue type hierarchy before modifying its structure as once these changes are made, they cannot be undone.

If you need assistance during this process, contact our support team.

0 votes
Felipe Silva May 2, 2024

Hi @Dave Mathijs , I'm looking for the same information regarding the impact. Were you able to figure this out?
I have 3 levels and I need to add a 4th. I thought this would have no impact as the new level is a new issue type.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events