I need to create a Report with EPIC, Feature and Story details

Greetings @achary_Santosh, and welcome to the Community!

James and Rustem have already covered the native options well. If PI is a custom field, filtering a Plan by that field and using "Show full hierarchy" can give you an Epic → Feature → Story view. If you need a more traditional report with fields such as owner, status, dates, and PI, Atlassian Analytics may be the better option.

Where this becomes more challenging is when PI-based reporting isn't a one-time request.

If you're coordinating multiple teams across an Agile Release Train (ART) and need this kind of visibility every PI, the problem starts to shift from creating a report to maintaining visibility across the PI itself: Features, Stories, dependencies, teams, and progress against the plan.

If your organization is using SAFe, this is also where a solution such as Agile Hive may be worth considering. Agile Hive maps SAFe organizational layers and work hierarchies into Jira, allowing work at the Portfolio, Solution, ART, and Team levels to remain connected as it moves through planning and delivery.

For example, the Agile Hive ART Planning Board provides a PI-level view across the ART, showing planned ART work, the teams involved, dependencies, and the expected delivery timeline. Team Planning Boards provide the corresponding team-level view, including the team's planned work, capacity, and cross-team dependencies within the selected PI.

That said, Agile Hive is a different investment than creating a saved filter, Plan, or Analytics dashboard. If you're primarily managing PI as a field on a backlog and need this report for a single team or project, the native Jira options already suggested here are likely the simpler solution.

If you're coordinating multiple teams using SAFe and this report is really part of a larger need for ongoing PI visibility, Agile Hive may be worth a look.

And in full disclosure, I work at Seibert Group GmbH, the team behind Agile Hive.


Thanks and best of luck!

Joshua
Content Writer & US Representative
Agile Hive & Aura Apps (products of Seibert Group GmbH)

Hi @Achary_ Santosh,

Plans and Atlassian Analytics, as suggested here, should both get you there. If what you ultimately want is a tabular, spreadsheet-style report that you can filter by PI and hand to stakeholders, and you're open to solutions from the Atlassian Marketplace, this is a very typical use case for JXL for Jira, the app my team and I work on.

In JXL, you would:

• Create a sheet scoped to your projects (or an existing filter)
• Enable hierarchy to see Epic > Feature > Story nested in the table. Since Feature is a custom hierarchy level, you can define a custom structure that uses the same parent relationships as your Plans setup
• Filter the Epic level by your Program Increment field. Child Features and Stories stay visible, so one filter gives you the full picture for a PI
• Add any columns you need (status, assignee, dates, story points), sum values up the hierarchy, and export to Excel or CSV whenever someone wants a static report

Here is how such a hierarchy looks in JXL:

For transparency: I'm part of the team behind JXL.

Best,

Ivan

Hi @Achary_ Santosh,

Welcome to the Atlassian Community.

You should be able to create such report/view by using Plans. Have you tried that?

An alternative would be to create a dashboard in Jira that offers an overview of your PI, features, epics, etc. But for this, most likely you will need an app from Atlassian Marketplace.

If you want to try an app, with our Great Gadgets app you can create powerful dashboards in Jira for tracking PIs, epics, and features.

For your specific example, I would recommend using these gadgets:

• Work Breakdown Structure gadget - this can display the hierarchical view of your Epics & Stories along with selected fields such as estimate, assignee or PI

• Pivot Table & Pivot Chart gadget - this can display the overall progress of the Epics &  Features based on number of their child items or their sum of Story Points 

This is higly configurable; you can split by PI if you want:

• Release Burndown Burnup Chart gadget - lets your display a burdown at PI level, Epic level or Feature level along with the ETA forecast and milestones 

• Great Gadgets Controller - this is a gadget that allows you to filter the dashboard by a PI or other criteria so you can visualize the report for a specific PI or a sub-set of data.

So in the end you obtain a report in form of a powerful Jira dashboard that allows easily filtering by PI.  

You can find more examples about how to use these gadgets in the context of SAFe (with PIs, Epics, Initiatives)  in these articles:

• https://community.atlassian.com/forums/App-Central-articles/How-to-track-scaled-agile-SAFe-projects-in-Jira-with-Great/ba-p/1929694
• https://community.atlassian.com/forums/App-Central-articles/How-to-display-the-progress-of-Epics-or-Initiatives-in-Jira-or/ba-p/2858840

If you like this solution I would be more than happy to assist you in configuring our app gadgets.

Danut.

Hi Santosh,

The approach depends on one thing you'll want to pin down first: how is "PI" actually stored in your instance? It isn't a native Jira field, so it's usually one of three things, and each one changes the answer:

1. A custom field (single-select, "PI 24.3" etc.) — most common outside Jira Align
2. A Fix Version naming convention — versions named per PI
3. A Jira Align construct — if you're synced to Align, the PI lives there, not in Jira

Also worth confirming: is Feature a real custom hierarchy level above Epic (Enterprise supports this), or an issue type sitting alongside Story? That determines whether you get true nesting or a flat list.

If PI is a custom field and you want it quickly:

Use a filter plus the list view rather than a "report" per se:

project = ABC AND "PI" = "PI 24.3" AND issuetype in (Epic, Feature, Story) ORDER BY issuetype

Then in the issue navigator, switch to List view, add columns for Parent, Status, Assignee, Story Points, and group by Parent. That gets you Epic → Feature → Story context in one screen, and it exports cleanly to CSV for anyone who wants it in Excel.

If you have Advanced Roadmaps (Premium/Enterprise):

This is the better fit for a genuine hierarchy report. Create a Plan scoped to the relevant boards/projects, then in the Scopeview set the hierarchy range to show Epic through Story. Filter by your PI field, save the view, and share it. Unlike the navigator it renders actual parent-child nesting, and if Feature is a custom hierarchy level above Epic it'll respect that. Docs: https://support.atlassian.com/jira-software-cloud/docs/configure-custom-hierarchy-levels-in-advanced-roadmaps/

One caveat on Fix Versions: if PI is encoded as a version, fixVersion doesn't inherit down the hierarchy — an Epic tagged to a PI doesn't tag its Stories. You'd need an automation rule to stamp children on create, or you'll get an incomplete report and not notice.

If you need a true nested matrix with rollups (sums by Epic, per-PI columns), the native tooling runs out and Structure or BigPicture is where most teams land for that shape.

If you can say which of the three PI setups you have and whether Feature is a hierarchy level or an issue type, I can give you the exact JQL and view config rather than the general shape.

Hello @Achary_ Santosh 

Before building this, I’d clarify two things first: What exactly is “PI” in your Jira?
Is it a custom field such as Program Increment, or is PI itself a work item above Feature in the hierarchy?

Since you’re on Cloud Enterprise, Atlassian Analytics is probably the best fit if you need a flat report showing PI, Feature, Epic and Story details together. 

If PI is a custom field, you can filter the Feature/Epic by that field and then bring in its descendants through the hierarchy.

If PI is a work item above Feature, the Work item hierarchy table is even easier, since it already contains ancestor/descendant relationships.

If you can share how PI is represented in your instance and the exact hierarchy, I can suggest the exact setup/query.

Hola Santosh,

Since you’re on Jira Cloud Enterprise, there are a few native ways to approach this, but the right one depends on how your hierarchy and PI information are modeled.

If Epic > Feature > Story is an actual hierarchy configured in Jira Plans, then Plans is probably the first place I’d look. It can show the hierarchy across those levels and let you filter the plan by fields that are present on the work items.

The key question is how you’re representing the PI. If PI is a custom field, Release/Fix Version, or another field on the work items, you may be able to filter the plan directly by that value. If you need a more formal tabular report with columns for Epic, Feature, Story, status, owner, dates, estimates, and PI, Atlassian Analytics may be a better fit on Enterprise because it gives you much more control over the output.

Could you clarify two things?

• Is Feature a custom hierarchy level between Epic and Story in Plans, or just a normal work type?
• And how is PI stored today, for example, a custom field, Fix Version, Release, or something else?

Once that’s clear, we can narrow this down to the simplest native option rather than overbuilding it.

Thanks,

James