I've been asked by our team of Scrum Masters as to best way to group a related set of Epics, for reporting/filtering. I'm not sure if others have encountered this need. * One thought is to create a new field such as "Super Epic" and then use that field within each Epic's definition page to assign it to the same Super Epic name. * Another thought - I've seen just a bit on Components, but haven't read much yet on that. Any suggestions? If it matters, we have the cloud version and I have encountered other limitations with that version, so just mentioning.

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

"Super" Epics?

Victoria Danner

I've been asked by our team of Scrum Masters as to best way to group a related set of Epics, for reporting/filtering. I'm not sure if others have encountered this need.

One thought is to create a new field such as "Super Epic" and then use that field within each Epic's definition page to assign it to the same Super Epic name.
Another thought - I've seen just a bit on Components, but haven't read much yet on that.

Any suggestions? If it matters, we have the cloud version and I have encountered other limitations with that version, so just mentioning.

Accepted answers

unknown

Hi @Victoria Danner

Components would fulfil the grouping aspect of this or a Label. Though I would ask, what reports are you trying to get?

Another method is using portfolio for JIRA or a similar addon to create Initiatives that are pretty much a “super epic”.

Let me know your reporting requirements and we as a community can better tailor our solutions for your requirements.

Hope this helps

Bastian Stehmann

Hi @Victoria Danner ,

I think there are a lot of ways to achieve this.

You can use a custom field as you already though of.

You can also create another issue type "Super Epic" and link the created issues using the link issue feature.

And there are apps, that will make it easier, for example Structure (available as early access program here

https://mailchi.mp/almworks/structure-cloud

Or Portfolio https://marketplace.atlassian.com/apps/1212136/portfolio-for-jira?hosting=cloud&tab=overview

All comments

unknown

Hi @Victoria Danner

Components would fulfil the grouping aspect of this or a Label. Though I would ask, what reports are you trying to get?

Another method is using portfolio for JIRA or a similar addon to create Initiatives that are pretty much a “super epic”.

Let me know your reporting requirements and we as a community can better tailor our solutions for your requirements.

Hope this helps

Bastian Stehmann

Hi @Victoria Danner ,

I think there are a lot of ways to achieve this.

You can use a custom field as you already though of.

You can also create another issue type "Super Epic" and link the created issues using the link issue feature.

And there are apps, that will make it easier, for example Structure (available as early access program here

https://mailchi.mp/almworks/structure-cloud

Or Portfolio https://marketplace.atlassian.com/apps/1212136/portfolio-for-jira?hosting=cloud&tab=overview

Victoria Danner

Very good point on reports and thank you. Although honestly we're not so evolved yet where we actually have a firm handle on reports. We just know this is data we'd like to capture for grouping and hope it will ultimately be of value in reporting, once we get to that.

Victoria Danner

In the interest of timing I went with custom field and hope that will address our need - at least for now. I'm not sure "Structure" is available in the Cloud, but will check it out as a potential future option. Don't think we're ready for Portfolio at this time - still trying to master the Agile Scrum and Kanban boards. Thank you!

unknown

I hope you get the reports you need @Victoria Danner

Egor Tasa [ALM Works]

Hi Victoria,

Let me put my two cents in here on behalf of Structure's developer, ALM Works. The launch of Structure Cloud is planned for the spring of 2019. To that end, the first Early Access Program (EAP) release was on January 15th, 2019. If you'd like, you may request access to Structure Cloud EAP releases via this page.

We would be happy to hear your feedback. If you're willing to share it with us you may also ask to join the Structure Cloud EAP on that page.

Regards,

Egor Tasa

ALM Works

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud