In the rapid board, (using scrum) a story is being burned down when it is marked closed.
I have inserted another column before closed (called testing, which otherwise works correctly) with relavent 'testing' status
Is there a way for the task burn down to occur at this stage rather than when the task is changed to the closes status,
As development burndown is determined by the development team making the code available to the QA team rather than the QA team later confirming that the item is correct.
"GreenHopper does support burning points. When you complete the story the points will be burned. As Tommy points out the right hand side column is your definition of done, so once a story is done it will be burned."
since the defination of done is fixed the requirement is not achievable...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot