Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Epic burndown accross multiple PIs

Epic level burndown from Program Increment Progress is useful but it only let's me pick one PI. Since Epics are assigned to multiple PIs, it would be useful if we could generate Epic burndown encompassing all PIs assigned to it.

2 answers

2 accepted

2 votes
Answer accepted
Tom O_Connor Atlassian Team Jun 18, 2020

From my experience, a burndown chart is useful when you know all of the work required to get it to done.  For stories, we define all of the work (stories and tasks) for the iteration.  For features, if we do effective PI/Big room planning we define all of the work (stories) for the PI/Quarterly timebox.  

Because the Portfolio Epic can cross multiple PIs and with the approach of incremental definition of development and delivery, we may not define all the work that we need to do as part of the epic.  We try to avoid big up front definition for epics so we may not define all features and stories to get it to done.  We may only create some feature placeholders and as we validate our value of the work we do, we may adjust, pivot or even stop development of the epic.  That said, a burndown chart for epics may not be effective.

If you are passionate about this request, submit an enhancement request in our   

1 vote
Answer accepted


You may want to consider using the Portfolio Epic Planning Function - 


From any Portfolio Epic - in the Right "Links" section of the Portfolio Epic, click "Portfolio Epic Planning" 


This view provides you a burndown based on the forecasted team/member weeks estimated for the Epic and it's associated child Features.  This view does require that at a minimum the portfolio managers are "SWAG-ing" the Epics in Team/Member weeks and the Product Managers are doing the same at the feature level. 


Remember:  Business Agility requires refinement of estimates as part of the decentralization of duties/decision making. 


Pro Tip:  Don't forget to use these estimates (SWAGs) as part of your train & portfolio I&A sessions in order to improve continuously! 

Thank you so much @Tina Behers . This is fantastic. I did not know about this feature!

Glad to be of assistance!  There are loads of little "hidden gems" in Jira Align it took me 5 years to find them all! 

Like ytoeda likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Align

Best Practices in Jira Align

Hello Jira Align customers! In order to better serve you on your journey with Jira Align, the Community team has worked with the Jira Align team to curate the content in this collection to better s...

623 views 1 11
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you