nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible to use hierarchy, Epic -> Capability ->Feature -> Story in Adv. Roadmaps?

Liz Craig

Using Jira 8.16 Data Center Advanced Roadmaps, added custom hierarchy Epic -> Capability ->Feature -> Story.

Want to create plans in AR using Project Capability and Feature.

Epic is linked to Capability by Child link
Capability is linked to Epic by Parent Link, and uses Child link to Feature
Feature is linked to Capability by Parent Link, and uses Issues Link to Story/subtasks

Is it possible to create a plan that uses Capability(Project) and Feature(Project) as sources and shows all Capabilities with it's Feature children?

Comments

Joseph Chung Yin

@Liz Craig -

Welcome to the community. Unfortunately, your configuration will not work with AR for Jira.

Without AR for Jira - The standard hierarchy for Jira Software out of the box is

Epic

>>> Story (any other standard issue type, ie: Task, Bug etc) - roll up to Epic via Epic link.

>>>> Sub-task (any other subtask issue type etc) - roll up to Epic or any other standard issue types as subtask (child)

This out of the box cannot be changed.

Parent link roll up can only be done above EPIC. So Story issues cannot roll up via this method to Feature.

It means that Feature/Capability issue types will be above Epic - where you rollup Epics to them via Parent link. Your Story issue type will roll up to Epic via the standard Epic link out of the box.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Liz Craig

Thank you for the information and your reply! I have another question, that I hope you can provide guidance/insight.

I modified the AR hierarchy configuration the the following. Even deleteing the Epic in the hierarchy did not solve the issue mentioned above.

Epic -> Feature
Capability -> Capability
Feature -> Feature
Story -> All other standard issue types
Subtasks -> All sub-task issue types

With the above hierarchy, I was able to create a plan with Epics and Capabilities (Project sources), displaying Epics & Capabilities. Also allows expansion of Epics to show children (Capabilities).

Why does this work for the Epics and Capabilities plan?

TIA

Joseph Chung Yin

Looking at your existing setup, it looks like you have just included

Capability issue type + Feature issue type to roll up to Epic issues.

Based on this, all you are doing is adding other new standard issue types to roll-up to Epic. The roll-up is done via Epic Link.

Can you take a screenshot of your issue hireachy configuration image and post it to this ask?

Best, Joseph

Liz Craig

Hi Joseph, I am unable to provide a snapshot but did recreate what the Hierarchy configuration looks like in AR:

# Level Name Jira Issue Types Actions

1 Epic Feature Remove

2 Capability Capability Remove

Feature Feature

Story All other standard issue types

Sub-task All sub-task issue types

Hope this information helps.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

advanced-roadmaps