Is there a way to show a EPIC burndown across multiple PI's and filter down to a product level?

[Oliveira_ Dano]

Currently when I look at reports for burndowns, I am only able to see them per PI.  I would like to see the view of this Epic that spans across multiple PI's so can see if when the epic will be delivered.

Is there a way to show an EPIC burndown across multiple PI's and filter down to a product level?

[Peter Jessen]

Hi @Oliveira_ Dano ,

You have several options to visualize what you are looking for.

• I assume you are interested in the portfolio epic vs the Jira epic, which is a feature in Align. features (Jira epics) cannot span multiple quarters in Align, while the portfolio epic can span multiple PIs and multiple programs/trains/teams-of-teams.
  • This point may appear obvious, yet it is one of the most common mindset shifts needed when integrating Jira with Jira Align because Jira epics have no time dimension and often are open for a year or longer prior to integrating with Jira Align.

One of my favorites is the Epic Planning Report, which is found in the blue menu on the right side of the details tab of the epic. 

• Here is the related help article - 10X: View the Epic Planning Report – Jira Align

Another option is to use the Strategy View of the Work Tree filtered on a specific epic.

• Here is the related help article - 10X: Work Tree (Strategy View) – Jira Align

You can also use the drill-down view by epics of the PI Progress report if you add all of the PIs/quarters to your top filter. 

One of the major issues/challenges of what you are wanting to see is that Align is looking at story points attached to stories on the features tied to the epic. 

• If all of the stories aren't defined with points for all features for the epic, then you aren't going to get meaningful views.
• And if you do plan out all stories with points for all features tied to the epic over the epic's lifetime, then you aren't operating in an agile manner, imho.

Another approach is to plan out all of the features on the epic across however many PIs the epic takes to complete. Add estimates on the features (I recommend estimating in pure story points vs weeks) and use the forecast functionality to ensure the trains and teams have the available capacity to complete the epic in the timeframe desired.

There are a few other options, but each would require more context.

Regards,
Peter