can the epic burndown report pull user stories for nested epics

JB Barnes September 14, 2022

Can the epic burndown report pull all user stories and issues for nested epics.

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 14, 2022

Hello @JB Barnes 

Welcome to the community.

Please explain what you mean by "nested epics". Jira does not natively support making one Epic a child of another Epic.

JB Barnes September 15, 2022

Hi @Trudy Claspill !
So, I created a parent epic and made it 'is parent to' two separate epics.  I'd like to see all of the issues together to get a view of all of that work.  If this isn't the best way to do this in Jira, is there a better way?

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 15, 2022

Hello @JB Barnes 

How did you add the "is parent to" relationship?

Can you provide a screen image of that parent epic that shows the relationship to the "child" epics?

Jira does not natively support "nesting" epics in a manner such that you would be able to "roll up" the information in native Epic-oriented reports.

If you used the native generic issue linking feature then you will not be able to roll up the information through the built in Epic Burndown.

To be able to create an issue at a higher level than Epics that can contain Epics as children would require either upgrading to the Premium subscription and using Advanced Roadmaps or implementing a third party app that supports extending the issue hierarchy. The buiilt-in Epic Burndown would still be unaffected by such extensions, but there might be other report that could provide burndown information for that higher level "parent of Epics" issue.

JB Barnes September 15, 2022

Got it.  We did use the native, "is parent to" functionality, just like you would for a user story.  It sounds like that isn't something that is commonly done.  We also have an initiative issue type and boulder issue type that we use as a higher level than epic.  It sounds like those won't really provide any functionality from a reporting and board perspective for us either and that out of the box Jira doesn't have a higher level than an epic and doesn't support nesting epics without going to a premium license. Thank you for your help.    

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events