Why won't my burndown update by completed issues? I have a Done Status to the rightmost of the Board

[Ogburn, Dustin]

I have a scrum board for one of my teams, it has 5 columns, each containing a few statuses.

The Done columns houses 'Completed' status types, and in this case the ticket to in the Done column has been marked as resolved. The Done column is the rightmost column of the board.

Simplified Status workflow is not enabled as we have a few issue types with different workflows

When I view the burndown, I expect to see the Done item burned down (burndown by issue count is shown) . I see the items I added to the Sprint, but am not seeing the one that should be marked as completed.

Does anyone know why this is occurring?

I've made sure the Done status is a 'Completed' Status, that the ticket has been 'Resolved', made sure that the Done column is the rightmost of course. I Have refreshed the board & report since.

[Martin Dowie]

Having this exact same issue...but just in one project...did you find the solution to your problem?

[Dam]

Hi @Ogburn, Dustin ,

Jira doesn't use the status to mark issue as done or resolved, Jira is using the Resolution field for that. If your burndown chart is not updated its because your issue are using the status Done, put you need to set the Resolution field as well. 

Here is a doc that explain it all: https://confluence.atlassian.com/cloudkb/best-practices-on-using-the-resolution-field-968660796.html

The "Resolution" field is an important feature in Jira. It specifies the reason an issue is closed and removes the need of having multiple statuses with the purpose of stating why the issue is closed, thus capturing important data for your team while reducing the time you have to manage your workflow.

Jira considers that the lifecycle of an issue has come to an end when the "Resolution" field has a value.

I hope it helps. 

Cheers,
Dam. 

[Ogburn, Dustin]

Thanks Dam, I did mention I have the ticket set as Resolved -  Resolutions status also 'Done'

[Dam]

Oh ok... So it's not the Resolution field.

Then do you have a specific field for Story point? or are you using Time based estimation? You need to configure the scrum board with the proper field for Story point or Time based... @Ogburn, Dustin 

Here is the doc to check this config on a board: https://support.atlassian.com/jira-software-cloud/docs/configure-estimation-and-tracking/

Cheers,
Dam.

[Ogburn, Dustin]

Thank you , I tried that and thought I had success - false celebration , but identified a new aspect of the problem

I switched The Basis of Estimate to Issue Count, and have identified the problem with burndown seems to be a unique case for a single ticket. (Story)

Another (defect) has since moved to 'Done' , and updated the burndown accordingly

However the original story I've moved to 'in-progress' and to 'done' for testing, and it registered the initial move back to 'in-progress' as a sprint addition - but did not register the move to 'done' as an item completion

You can see in the chart where the 2nd ticket completed (was burned down) and the first ticket was moved back to 'in-progress' (chart spike up) but then there was no burndown when the 1st ticket was moved back to done. So currently this ticket only has the ability to "add scope" to our sprint

I'll continue testing other stories through the sprint. These 2 issues are of different type (defect burned down, story did not), but follow the same workflow and have the same fields completed

[Dam]

Ah I see... All issues should burn down the burndow chart when they are done (with resolution field set). There is maybe some different workflow depending on the issuetype in your project... You need to set the resolution in all workflows on Close or Done status for all issue types. 

At least I think you have some good leads to find your configuration problem, cause it's just a problem of configurations in your project ;)

Cheers,
Dam.