how to report burndowns for project, increment and releases...?

Question

so Jira has a release and epic burndown, but what I also need to view is the project and increment burndown.

ie: each project will have 2-3 increments

each increment will have multiple releases

each release will contain multiple epics.

is there a way in Jira to do a burndown for the project and increments? or a plug in that would enable this?

thanks in advance

Evan Golden {VisualScript} · Answer

Charlie

Another add-on available that can be used to meet your requirements is VisualScript for Jira.

It has a built-in sprint burn down report, but is a tool that has the ability to create custom reports in Jira dashboard gadgets.

These reports can be increment burndown, PI burndown (if using SAFe), and project burndown.

The script can have a start date, end date, and project key(s) parameters, as an example, that once entered will find the data and relationships to create the visual report.

FYI - I work in the VisualScript product team.

Thanks

Evan

Marianne Miller · Answer

There are a few plug-ins that might report at this level, that report by project or filter.

https://marketplace.atlassian.com/search?query=burndown

If the filters need to be built anyway, I think you would be able to do this with custom boards if you can define this breakdown.  It's a pretty manual process, but you could manage it.

Create a JQL Query to define the release

Release_Filter1:  Project = XXX and Epic Link in (AAA, BBB, CCC)

Etc

Do this for as many epics as you are batching

The create a JQL Query to define the Increment

Increment_filter:  filter = ("release filter1") or filter = ("release filter2")

Etc

To build the project level filter, filter for the increments

Project filter: filter = increment1 or filter = increment2

etc

Create a new board for each "master" level query.  (Eg board for each release (multiple epics), board for each increment (multiple releases), board for project (multiple increments)

Go to Boards and select the new board.  Switch to reports view in your project. The burndown chart should reflect the multiple epics in a release.  You can still view by Sprint and Change the Y axis to a relevant field.