We have programs (logically) which is a group of JIRA projects, is there a way to get epic and story burndown charts for the program as opposed to per projects?

[Santak]

We have programs (logically) which is a group of JIRA projects, is there a way to get epic and story burn down charts for the program as opposed to per projects?

So say we have five projects grouped as a program, we need to have the epic and story burn down charts for the program, we can get the individual burn down charts per project but need them aggregated so that we have a consolidated chart for the program.

We are currently using JIRA with Agile v6.2.4 with the upgrade planned for this year.

[David Goldstein · Accepted solution]

JIRA's core reports are very limited and JIRA Agile/Software's reporting highly targeted at single board or single-project reporting.

One straightforward option is to configure your JIRA Agile boards for sprint planning and management of active sprints to incorporate all the stories from the multiple projects.  That will give you access to burn downs across the program.  The downside is you may find too much entanglement of sprint planning and backlog grooming with the various project and program managers all working off a single JIRA Agile board.

Another option is to look at an enterprise-grade, commercial reporting add-on for JIRA like our Arsenale Dataplane for JIRA product.  With Dataplane you can create burn down, burn up and cumulative flow diagrams and much more across any arbitrary selection of projects, filters or Agile boards in your JIRA instance.  

Here are a few Dataplane report examples you may find useful:

• creating multi-project JIRA burn up charts (burn downs are just a variation on this)
• creating program cumulative flow diagrams

And an example of a Dataplane burn up chart across multiple projects, broken down further by issue status and issue type:

dataplaneForJIRA.jpeg

[Steven F Behnke]

You can obtain burndowns from a Sprint, a single-project's Version, or an Epic. There is no way to combine multiple projects for reporting from JIRA Reports. 

Why do you have a single product split across 5 projects? That seems very 'heavy.'