Adding multiple Issue Type in Jira Hiearchy

[Tam Do]

Hello,

We currently use the default work type hierarchy: Functional Area → Initiative → Epic → Story → Sub-task (attached).

Recently, we added custom Jira work types to align with our organizational needs and team terminology, with custom schemes depending on the issue type. We would like to add these custom work types to the Jira hierarchy so we can leverage the built-in functionality (e.g., timeline).

Jira has a setting that allows associating multiple work/issue types at the same hierarchy level, but my concern is whether adding a new work/issue type will break any existing linking. For example, if I add my custom work type Agency to the Epic level, will this break any existing links between Epics and the new Agency type? And will my custom work types inherit all the built-in Epic functionality?

[Evgenii]

Hi, @Tam Do 

You can add new issue types to hierarchy and it won't affect on any existing issue links. It's just expansion of hierarchy tiers. 

And now there is no Epic terminology. It's deprecated. All issues have parent-child issue linkage through Parent field.

[Tam Do]

Hi @Evgenii ,


Are you saying that adding a new Issue type to the hierarchy (Epic) will deprecate the existing Epic hierarchy setting?

[Evgenii]

No, absolutely no.
I was talking, that field Epic Link, is now deprecated. 
I'm telling, that Epiс now - is just issue type, which is above ordinary issues. 
You can add another issue type, and add it to hierarchy level, where Epic is located, and it will have absolutely same functionality.