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; } } }

Epic Feature Story Hierarchy?

Tej_r8jhlw

Hi,

Here Initiative Epic Feature Story Task is the Hierarchy want to achieve.

Portfolio take care of Initiative-Epic

The problem comes with Epic-Feature-Story, how to achieve?

With Structure plugin, I linked Epic Feature and Story but the problem is when I update story tickets there's no progress in Epic in the Agile Backlog Board, epic progress gets updated only when the feature is updated there's no relation between stories and epics now.

I don't think we can rename default Epic Issue Type and change it to Feature?

Dave

Accepted answers

Eugene Sokhransky _ALM Works_

Hi Dave,

You can actually change the name of the Field that will work as an Epic on Agile boards to anything you want, including Feature.

The parameter that makes JIRA treat the type as Agile Epic is Description, which says: gh.issue.epic.desc

Here is an example of such setup:

https://structure-safe-jira.almworks.com/secure/StructureBoard.jspa?s=197&os_username=demo&os_password=demo

As for rollin-up progress, you should be able to see it in Structure. If something doesn't work, please let us know and we'll be happy to look into it. You can leave a comment here or open a ticket in our JIRA:

support.almworks.com

Thanks,

Eugene (ALM Works)

All comments

Eugene Sokhransky _ALM Works_

Hi Dave,

You can actually change the name of the Field that will work as an Epic on Agile boards to anything you want, including Feature.

The parameter that makes JIRA treat the type as Agile Epic is Description, which says: gh.issue.epic.desc

Here is an example of such setup:

https://structure-safe-jira.almworks.com/secure/StructureBoard.jspa?s=197&os_username=demo&os_password=demo

support.almworks.com

Thanks,

Eugene (ALM Works)

Tej_r8jhlw

Thanks a lot for help.

good to know, about gh.issue.epic.desc

Deni Christopherson

Hi Dave,

I was curious if you ended up just using Portfolio and changed the name of Epic to achieve your desired hierarchy? Or if you ended up using Structure. I was about to do a similar test using Portfolio and was just curious of your outcome.

Thanks,

Deni

Eugene Sokhransky _ALM Works_

Hi Dave, Deni,

A quick update on the Strucutre side - we've added support for Portfolio Parent links so you can now use two tools together (most customers would use Porfolio for planning and Strucutre to tracking and other everyday activities).

Here is a series of blog posts covering this use case. Maybe it will be useful for you:

http://almworks.com/blog/2017-01-track-portfolio-plans-real-time.html

Regards,

Eugene (ALM Works)

Magnus Johnard

I am also looking for a view showing this simple hierarchy since my pieces of work are that big and need the break down to be small enough in a sprint. How can you make that visisble in Structure or Portfolio?

It is a quite basic requirement.

Vlad[ALM Works]

Hi Magnus,

Thanks for your post.

If you could share a bit more information about your specific hierarchy (Issue Types used, how many levels etc...), I'd be more than happy to make some recommendations.

But as an example, you could take advantage of Structure's Automation Feature to bring your Epics into a structure, using the Insert Generator. Once you do that, you could use the Extend Generator to visualize Stories under Epics, Linked Issues under Stories, and Sub-Tasks as needed. You could even Group your Issues by Sprint after that.

I wanted to briefly mention how Structure could help you visualize your Jira issues but I'll be more than happy to address your particular case in more detail if you'd like. I can be reached at vlad@almworks.com and our Support Team is always eager to help at support@almworks.com.

I look forward to hearing back from you.

Best Regards,

Vlad

[ALM Works]

Magnus Johnard

Hello,

As a PO I just want to get a default view of the following SAFe tree structure. I want to be able to drill down in the tree structure down to task in one view so I quickly can overview what is planned and refined.

Epic

Feature
- Story
  - Task (Dev, Test, etc)
  - Bug

Vlad[ALM Works]

Hi Magnus,

There are a couple different ways to achieve this. I recommend using the Automation Feature to get to the desired results. For instance, you could start by Inserting your Epics into the structure:

Automation > + > Insert > JQL Query: Type = Epicor Type = Epic and Project = YourProject (in case you need to be more specific)
You would then bring in the Features under the Epics. For that, you'd use an Extender: Automation > + >Extend > Choose the right option - choose the appropriate option ("Stories under Epics" if Features are linked to Epics with Epic Links or "Linked Issues" if there's a particular Link Type used in Jira between the 2 Issue Types.
Show Stories under Features: Automation > + >Extend > Linked Issues - All available Link Types in Jira will be presented as options to choose from. You will also get a chance to set the Link Direction and Extend Levels (level 3 applies here to show Stories under Features)

Simply repeat step 3 to show Tasks and Bugs under Stories by choosing the appropriate Link Types.

Note: Please always make sure you're focusing on the top level of your structure (the row with your structure's name will be highlighted in blue) to ensure that the Generators are being properly applied to the whole structure.

I hope this helps. Please let me know if you need further assistance. Our Support Team can also be reached through our Service Desk portal by emailing support@almworks.com.

Best Regards,

Vlad

Isaac Sacolick

I'm also trying to get a hierarchy that looks like epic->feature->story. I want Epics to work as/is in Jira (ie, epics on the rails for navigation), but also ask POs to break epics down to features and then stories. I have some rationale behind this and can explain it to anyone interested.

Reading through these comments, I can see renaming the epic issue type to feature and then use Portfolio to create a new epic type that lives above feature. This isn't elegant because I lose the epic level navigation in Jira because it would be more granularly defined w/ Features. Also, I have to apply this to projects that are in progress, so it would take some work to realign the hierarchy.

Is there a better approach? I haven't tried the Structure plugin.

Thanks!

Vlad[ALM Works]

Hi Isaac,

Thanks for posting.

How are your epics linked to features and features to stories?

Structure allows you to visualize issues based on a hierarchy you define. This is done using the Automation feature, via Generators, specifically the Extend Generator.

If you don't want to go down the recommended path of renaming the epic issue type, and you're willing to use an app, we can discuss your use case further so we can make a recommendation.

Our support team is always eager to help and can be reached at support@almworks.com.

Best Regards,

Vlad

ALM Works

Chris Hansen_qark4e

I'm constantly amazed how Jira fails to address product management principles properly.

Being forced to programmatically customize Issue types into various themes is a LOT of overhead.

Being forced to buy add-in SaaS solutions (Structure, now ALMWORKS) to address the lack of hierarchy (and then to have to customize this add-in once again) is a giant PITA.

TFS/AzDO has this nailed, and it's OOTB. I put together the backlog and structure / heirarchy I wanted in AzDO in <30 mins. For JIRA, I'm still struggling with the instructions. It will likely take HOURS to resolve this.

Meanwhile, my SM, Dev and QA team are waiting for me to finish my work so that we can kickoff my product.

Not a fan.

Isaac Sacolick

Chris - Azdo definitely has the better solution by making it easy to implement Features as in Epics->Features->Stories. After that one benefit, I find Azdo a "good enough" solution only if working with few teams and simpler architectures. The reporting is only acceptable if you use PowerBI and even then it isn't great. It's also harder to create a healthy blend of where teams can self-organize versus where you want standards.

Happy to share with you how I implemented Features and to make Jira easier to work with for product managers. Just a handful of one-time setup steps.

Alok Juneja_1ug6qy

Hi @Isaac Sacolick

i would appreciate if you please share your approach to create epic - feature - story hierarchy.

br,

alok

alban.kit.partner

I m so disappointed about JIRA : how is is possible that you can't organize by Epic>Feature>Story>Task ? It's not an amazing feature ...

So i have Feature>Story and I use a tag to identify an Epic 👎

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

jira-administration

structure

hierarchy

feature