How do I set up the right hierarchy using Structure plugin?

[Ashkhen Avetisyan]

My company is using an OKR approach so we need an additional level of hierarchy above our basic Epic-Task-Subtask structure. While I don't aim to add new issue types, it has been decided to use Structure to link Objectives and Key results with corresponding epics.

I've tried creating Objectives as epics and KR's as tasks and link them to existing epics and issues with parent-child link type. However after using generators it occurs that the epics are duplicated in the structure because of extending structure with two link types.

Is there a way to add a level of hierarchy above epics without creating new issue type or duplicating items? Maybe creating a project with objectives and KR's and linking issues to other projects will help?

Here is the structure I need (a multi-project view as well):

Project A

 - Objective A1  

      -- KR1

      --- Epic 1

      ---- Task 1

      -- KR2

      --- Epic 2

      ---- Task 2

  - Obejctive A2

     -- KR2

     --- Epic 2

     ---- Task 2

Project B

 - Objective B1  

      -- KR3

      --- Epic 3

      ---- Task 3

      -- KR4

      --- Epic 4

      ---- Task 4

[Kelly Arrey · Accepted solution]

Hi @Ashkhen Avetisyan, @Clark Everson's advice is very good. Also, I did a webinar on setting up a hierarchy in Structure in case this helps. We use a custom issue link type we call "contains <-> belongs to" instead of Parent links, because we like the flexibility of being able to skip a layer of the hierarchy, or for issues to have two parents in some situations.

[Ashkhen Avetisyan]

Hi @Kelly Arrey

Thanks for your help! We probably need flexibility as well and certainly have a few issues with multiple parents (i.e. issues that contribute to reaching multiple Key Results), I guess creating a custom link type will be a great idea in that case

Your webinar seems to be very insightful, by the way – looking forward to finding some time to watch it!

[Clark Everson · Accepted solution]

Hi @Ashkhen Avetisyan 

Welcome to community!

You would need to add issue types. Even in Advanced Roadmaps, Atlassians platform you need to create additional issue types. One Issue type can't serve on two hierarchy levels

Tasks and Stories are seen at the same level

This guide is helpful for structure: https://www.idalko.com/structure-for-jira/

And for atlassian even their best practices suggest additional hierarchy here: https://www.atlassian.com/agile/project-management/epics-stories-themes

Depending on what you are trying to do being too restrictive with issue types can be problematic. You do have the right idea in being restrictive but there is a difference between restrictive and too restrictive.

Based off your structure currently you need at least two new issue types which is normal. But if you need 3 or 4 that's also fine. However for every issue type above epic it's best to only have one issue type of that level to avoid confusion. That's the real key to a successful hierarchy.

Best,
Clark

[Ashkhen Avetisyan]

Hi @Clark Everson 

Thank you for the advice – now it makes perfect sense why it would be better (and easier!) to create new issue types instead of using same types for different hierarchy levels.

I think we'll just create new issue types for higher levels of hierarchy instead of trying to invent workarounds and make unnecessary (in our case) restrictions.

Thank you for the links, they are useful as well!

Best,

Ashkhen