What is the best way to create a release burndown chart involving multiple projects

[francis]

We want to create a release burndown chart on a rapid board.
The rapid board is configured with multiple projects (such that it lists multiple versions and multiple sprints)

Is there a way to create a kind of burndown charts, taking into account all issues ?

[Danut M _StonikByte_]

Try the Great Gadgets add-on:

• Jira Cloud: https://marketplace.atlassian.com/plugins/com.stonikbyte.great.gadgets.plugin/cloud/overview.
• Jira Server: https://marketplace.atlassian.com/apps/1218777/great-gadgets-for-jira-server?hosting=server&tab=overview

It offers a Release Burnup Burndown Chart gadget that is based on a JIRA filter. Put in that filter the issues from your project scope and group data by your sprint duration and you will have the burndown chart. Calculation can be done by Story Points, Issue Count or Original Time Estimates (hours) field.

Please note that I’m one of the folks behind StonikByte, there may be other solutions out there.

Similarly it can calculate the team velocity:

 

[mwarton]

Hi again,

The example templates only include a per project progress report with burn up chart, but you can either modify this reports rules or create a new report for your purposes.

In the modify chart rule you will simply want to specify a JQL query or filter that includes all the issues from all of the projects you want, or alternatively multiple JQL queries, one for each project you are interested in. A simple JQL query to get all rules can be "created is not empty"

See the charts section of the tutorial for more info on how to set this up. If you still have any problems let me know and we will create an example report for you.

Thanks,

Matt

[Wim Van Hoecke]

Using filters is indeed a good solution.

Can we also create charts based on eg story points (custom fiels in an issue)? Or can the charts only be based on counting issues?

Wim

[mwarton]

Charts based on story points (and any other numerical value) is part of the upcoming integration with JIRA Agile release. It should be available within the next few days.

[Wim Van Hoecke]

That's great news.

Will there also be an example template?

Wim

[mwarton]

Yes, some example JIRA Agile report templates will be included in the release.

Thanks,

Matt

[Wim Van Hoecke]

Any idea when these templates will be released?

Wim

[mwarton]

Hi Wim,

The release is now available. When you upgrade to version 2.3 or above the extra 2 sample templates, Sprint Timesheet and All Boards Progress Report will be installed automatically. More templates are also in development.

Thanks,

Matt

[mwarton]

Hi Francis,

Using our plugin Intelligent Reports you can create burndown charts across any collections of issues you like, including across projects. If you like you could even put separate lines on the same chart for each project, along with one for all the projects combined. You design your output chart formatting in Microsoft Word and then fill in the data from simple point and click rules, including full JQL for data selection. You can try it free, so check it out.

[Wim Van Hoecke]

Hi,

How can you do this accross projects? I can only select one project in the drop-down list.

Do you have an example/template for a burndown chart?

wkr,
Wim

[boardtc]

For a single project, you can access the Release Burndown by first selecting the project and then picking agile, or get it from the reports icon in the sidebar: https://confluence.atlassian.com/agile/jira-agile-user-s-guide/using-a-board/using-reports/viewing-the-release-burndown

Frustratingly, there is no way of changing the filter behind the reports in order to pull in multiple projects or to analyse a project which has multiple teams using.

Older versions of JIRA had the sprint burndown gadget which ran against a filter, removing that was a backwards step 

Please add your vote for the functionality to be added: JSW-10953

[Peter Van de Voorde]

Since Sprints now own an issue it's no longer possible to do this by simply creating a giant sprint that contains all the issues from the different project sprints.

Best regards,

Peter