Burndown - when Done is not Done

[Narelle Sartain]

Hi,

We are a on team managed project. I would like my burndown to be based on the cards that were Done in the sprint. But not just where the Status = Done. In my workflow, I have statuses that are categorised as a Done status. For example - Waiting to Merge is a status on our Jira Scrum board. It is not on the far right column, but it IS marked as Done from a workflow perspective. 

The burndown is ignoring that though, it just looks at those with an actual status of Done.

Is there ANY way to fix this? Previously I have created my own board ( an edited copy really) that is just to get a better report, and moved all statuses I need into the Done column of my Jira board. But on a Team Managed Project I don't see a way to have a different board that just I can see.

I don't really see the point of category otherwise.

Thanks

narelle

[Max Foerster - K15t · Accepted solution]

Hey @Narelle Sartain and welcome to the community! 😄

You can call it a lack of flexibility or you can consider it an intentional design decision to make it as easy as possible for users but only issues in the most-right column are considered "really" done. In Jira terms that means resolved. Having a resolution is the most important thing for Jira issues. Only then do most of the reports (and the interface) consider issues as really done. So there's no way around it.

Best, Max

[Nic Brough -Adaptavist-]

The design decision is right when you have a thorough understanding of how scrum works, but team-managed projects are definitely the problem here - as you say, they lack the flexibility to define your columns properly.