Sprint Burndown Modification

[Jacobssmith]

I would like to create a burndown chart where the story points are calculated based on stories in the "Ready for Testing" state rather than "Completed". For my sprints, the stories are not in completed state until the end of the sprint, making the OOB burndown useless. Is there a way to modify the widget to calculate the remaining story points for only the items in draft, ready, and work in progress?

[Andrew Barnes -]

Greetings Jacob,

 When I attempted to do something fairly similar a year ago, I was better off just building my own breakdown. The OOB process does not really make it easy to have two terminal states. Might I ask though, why yours are not completed until the end of the sprint? Given the state name - ready for testing, that implies someone is testing them, and then if tests pass, it is completed? That sounds like the end of the dev cycle on that record, not the end of the sprint. 

-Andrew Barnes
Join me at Developer Blog

[Benny Jensen]

Hi

I have the same question in our organisation on how to change the burndown calculation. We wish to track the burndown of the development since there are other groups involved in the testing. So the burndown out of the box does not show the efficiency of the developers. 

So if anyone with any idea on how to do this or if it's even possible?

//Benny

[Sonichka]

Hi there, 

Do you have news regarding the option to choose different states for "done" calculation? I have the same requirement and I'm struggling with all those script includes and instance metrics.

Thanks. 🙂

[frederictribole]

Hi, 

Same request, how to get the burndown based on stories in the "Ready for Testing" rather than "completed" ? 

Thanks for your help. 🙂

Fred.