The Epic hierarchy is a feature of JIRA Software, which itself used to be an add-on for JIRA.
It adds an Epic Link field to issues that are children of the Epic issue type.
I'm fairly certain it's impossible to apply that to different issue types using standard JIRA settings.
There's a very similar question with good answers here - https://answers.atlassian.com/questions/38385869
As Quentin Bellégo mentioned, there are numerous plugins that provide custom hierarchies.
You'll find that all of those plugins have plenty of additional features besides hierarchy. Structure (disc. - I work for its creators) for all sorts of management, reporting & overview; Portfolio for planning; Links Hierarchy is probably unrivalled for visualising complex linked relationships, etc.
Example screenshot from Links Hierarchy:
Hello, Sorry to comment on this old thread. Wanted to confirm that this is still true. So we cannot configure hierarchy levels higher than Epics (as detailed in the below link) using JIRA without installing any of the paid add-ons like Portfolio for JIRA ?
@Robert Leitch [ALM Works] : Thanks alot for you Reply. I am using Portfolio plugins for creating Hierarchy levels. The problem I am facing right now is that I am not able to add Epic (by default) in the Level List. Please find the image below.
Epic is already in the list, along with Story and Sub-Task.
Portfolio only puts numbers beside custom hierarchy levels, maybe that's causing some confusion?
You should be able to rename them and map them to different issue types:
If you're not able to edit those fields, then there's probably a permissions problem.
I don't think it would be a good idea to remap the Epic-Story-SubTask part.
If you definitely want to use Portfolio but can't use the prescribed configuration because it doesn't match your real-life processes, my recommendation would be to contact an Atlassian Expert (these are accredited partners of Atlassian) for assistance. It's very possible that you'll save time and money in the long run.
Robert Leitch [ALM Works] : Thanks alot for the reply. My concern is that I am not able to add "epic" in hierarchy level. I want it to be at level-2, after initiative but I am not able to move it. Thus when I am creating an issue on board >>> epic, I can't connect it with the initiative as a parent link (As I can't see the previously created "Initiative" in the "Parent Link" list). Please find the image below.
Robert Leitch [ALM Works] : Unfortunately No. Thats my major concern. I want to see that in the parent list as you mentioned the issue with issuetypes 'Initiative'. I believe the reason why I can't see is that the epic is not set as level-2 in my hierarchy as I can't move it under Initiative.
Ahh, okay... I don't see any problem with your Portfolio hierarchy - in the screenshot you shared, Epics are correctly positioned underneath Initiatives. I think I might know what's wrong (famous last words though...)
Sorry, I was looking at the wrong screenshot (my own) before.
Your Portfolio hierarchy is not right. You need to remove levels 2 and 3 so that epics come right under initiatives.
Then it will look like this and everything should work fine:
These will be your four levels.
It might make sense to rename your 'Epic Level-1' to avoid confusion with the default Epic level.
Robert Leitch [ALM Works] : Perfect !! Thanks alot for your time. I really appreciate. It is working now in the way that I wanted to do. I want to clarify one thing , will this hierarchy make changes in all the projects ? If so can I define different Hierarchy levels for different projects?
Glad to help Aarti, sorry it took me a while to spot the obvious problem.
Portfolio hierarchy is defined by issue types and is global for all Portfolio plans.
The hierarchy is not applied to projects in any way as far as I am aware.
JIRA requires that Sub-Tasks must be in the same project as their parent issues, but Stories, Epics, Initiatives, Themes, etc. can all be in different projects. They just have to be of the correct issue type for their level in the Portfolio hierarchy.
This documentation page might help to clarify - Configuring initiatives and other hierarchy levels.
In short - no, you can't define different hierarchies for different projects, nor can you explicitly map levels to projects. In Portfolio, level = issue type.
Update: I added some Portfolio tags to your original question to grab the attention of the Portfolio team, hopefully someone will be able to correct me if I'm mistaken in my explanation.
Robert Leitch [ALM Works] : Thank you so much. Sorry, one last thing, is it somehow possible to create an issue "story" and add it parent link as "epic level-1" not the "epic". ? Please find the image below:
e.g. I want to create a story and want to directly attach it with "Epic level-1" means in the parent link options, will it possible to see "initiatives" instead of "epic".
Introduction This article will give insight on how a small software development department implemented Atlassian products to enhance and streamline the business process. The privately held company h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs