Configuring the Agile Gadget to display burndown based on other status than CLOSED

Question

The Problem:

In our teams we are having the problem that our tests are performed a bit after the actual development is done. The effect of this is that the burndown is not burning,  since it is based on the fact that the issues needs to be CLOSED in order to give burn on the burndown.

We have a lot of things that are DONE but they are not tested until x days ahead.

Is there any way to reconfigure the Agile Gadget to burn down on DONE instead of CLOSED status and give the developer part and maybe the testpart separately?

Jakob Rödström · Answer

So, if we were to map "Resolved" to the Closed column (where status Closed is mapped) the Agile Gadget would burn when a status would be set to Resolved?

But how ever I am trying to figure this out, I end up with having TEST one step back in the process? "To-Do : In Progress : Test : Closed/Done"

That would mean that an issue needs to be moved back in the board to be tested after it has been resolved?

And, is this really applicable in the Classic Agile Gadget? Not just the Rapid Board Scrum Gadget?

https://docs.google.com/file/d/0B26prr2klGaFd0xjR2RpUDNNdzA/edit?usp=drivesdk

https://docs.google.com/file/d/0B26prr2klGaFYzNwX3ZlcjVDbTg/edit?usp=drivesdk

Jakob Rödström · Answer

We would really like to aviod this. TEST and team needs to be tighter, not more separate.

Henning Tietgens · Answer

Maybe you should split your board into one board for development and one for testing. The rightmost column of the boards define the done status for the burndown, so you can generate a burndown for development and (from the other board) a burndown for testing.

Henning