Issues moved to Active Sprint from previous one, then resolved, doesn't update Sprint Burndown

Question

Hello peeps,

I am having a problem getting issues that have multiple Sprints in the sprint field to update the burndown chart of the sprint they were completed in.

Example:

Issue ABC-24 was created in Sprint 6, was never completed during that sprint, was then moved to Sprint 7 when Sprint 6 ended, then was completed and resolved in Sprint 7.

The burndown chart for Sprint 7 and the automated Burndown chart in the board "Insights" section does not reflect that the issue story points contributed to Sprint 7.

There doesn't seem to be a way to remove the previous sprints from the Sprint field (for obvious reasons), but why isn't the default functionality that the story point completion contributes to the Sprint burndown of the sprint the issue is completed in?

Thanks for the help!

Nick Nader_v96rns · Answer

Yep, last column is Done. I have tried several "Complete" statuses, as well as all the Resolution types. Seems to be a bug

Danut M _StonikByte_ · Answer

Hi @Nick Nader,

Check the configuration of your agile board and make sure that the "Done" status is mapped on the last column of the board. Jira considers the issues as done, if they are in the last board's column.

If this does not help, you could also try our Great Gadgets app, which offers advanced burndown/burnup charts which will make your project tracking job easier and more efficient. See https://community.atlassian.com/t5/App-Central/8-gadgets-for-a-powerful-Scrum-dashboard-in-Jira/ba-p/1683063

Hope this helps.

Danut.

Nick Nader_v96rns · Answer

It would seem that this actually happens with any issues in my Active Sprint. I can create a completely new issue, add story points, and complete it in a "Done" status with "Done" Resolution, and the Insights Sprint Burndown removes the Story Points from the total "To Go" value rather than adding the Story Points to the "Done" total...