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

[Achary_ Santosh]

Hi Team,

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

This needs to be filtered via PIs 

[Rustem Shiriiazdanov _Actonic_]

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.

[Achary_ Santosh]

PI is the Program Increment . 
Yes,

I am looking for report PI wise so as to understand what EPICs and its corresponding work items .  

[James Gamble]

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

[Achary_ Santosh]

PI is custom field 
the hierarchy is correst as guessed . Its Epic >Feature > Story 

[James Gamble]

Hola Santosh,

That helps. Since PI is a custom field and your hierarchy is Epic > Feature > Story, I’d start with Plans rather than jumping straight to Analytics.

If the PI custom field is added to the plan and is one of the supported filterable field types, you can filter the plan by a specific Program Increment and then turn on Show full hierarchy. That lets you filter on the PI while still displaying the related Epic, Feature, and Story structure underneath it, even where the child work items themselves don’t carry the PI value. Atlassian documents that behavior here.

One thing to check is the type of your PI custom field. Plans support custom-field filtering for single-select, multi-select, checkbox, radio button, and label fields. If your Program Increment field is one of those, this should be fairly straightforward.

That would give you a good interactive PI-by-PI view of the hierarchy. If you ultimately need a formal table or export that explicitly includes PI, Epic, Feature, Story, status, owner, dates, and other fields, then Atlassian Analytics is the better option. Enterprise includes the Jira work item hierarchy data needed to relate descendants through their ancestors.

For now, I’d try the Plans approach first, as it seems closest to your goal of selecting a PI and viewing its Epics and corresponding work items without building a custom report.

Thanks,

James