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.
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.
Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...