Burndown Report Incorrectly Marking Issues as Reopened

[Gale Pollard]

Hello! 

I've been using the sprint Burndown chart under "reports" for my project. As we don't always estimate tasks, the most accurate measurement is by issue count, and I'll look at the sprint in progress to ensure we're on track. 

Bugs in my project have two different status in the "done" category: Done (dev has submitted a fix) and Verified (QA has verified that the bug is fixed). When a dev moves it to Done, the burndown report logs that it was completed. However, when QA moves it to verified, the report marks it as reopened!? It has an Event Type of Burndown and an Event Detail of Issue Reopened in the log. (I cannot provide screenshots for security reasons, unfortunately). Any idea why this might be happening?

[Bill Sheboy · Accepted solution]

Hi @Gale Pollard -- Welcome to the Atlassian Community!

For a Jira Scrum board, only issues in status values mapped to the far-right column are considered "completed" for the sprint.  The status category has no impact on whether Jira considers the issues completed for the Sprint.

Are your "Done" and "Verified" status values both in that far-right column?

Kind regards,
Bill

[Gale Pollard]

This fixed it. Thank you!

[Crimsalytics]

We solved this same issue with our custom burndown chart (when in story points mode) by looking at the status category (one of to do, in progress, or done).  When an issue enters a "done" status, the story is considered completed.  This allows users to flexibly define which statuses equate to done.  Here's a link to our gadget in the marketplace and the associated documentation within Jira about setting status categories.

One capability that we built that helps you understand what is happening in a burndown is the Analyze Burndown Changes feature.  It aggregates changes to every story on every day.  It basically shows you all of the points changes to the story including increasing or decreasing the story's size as well as zeroing out the number of points when the issue transitions to a "done" status category.  Below is an example.  You can filter the change list to the currently visualized date range in the chart or a manually entered set of dates.  From there, you can sort by issue key, date or story point change.  This also works for time-based burndowns.

[Danut M _StonikByte_]

Hi @Gale Pollard,

As Bill explained very well, the Jira burndown report considers as burned those issues that are in the statuses mapped in the last column (far right) of the dashboard.

Most likely this is the problem. So, please check if the Checked state is mapped in the last column of the dashboard.

If you don't want to alter your agile board, then you could look for a better alternative (a plugin) on Atlassian Marketplace.

If you want to try a plugin, our Great Gadgets app offers a Sprint Burndown Burnup Chart gadget that lets you configure what statuses to be considered as done.

The gadget offers also a Data tab with a detailed report similar to the one of Jira.

And the same app offers similar capabilities for gadget like team velocity, release burndown, etc. So you will have the entire suite of analytics for your project. See also https://community.atlassian.com/forums/App-Central-articles/8-gadgets-for-a-powerful-Scrum-dashboard-in-Jira/ba-p/1683063

Danut.