Hi, the title says it all really.
I've just come back from a day off to find that somebody removed a load of stories from the sprint and replaced it with a different set. Nothing really wrong with that, except that the new stories had no estimate against them. Consequently the burndown looks a complete mess.
Is there any way to prevent stories being added to sprints unless they have a Story Point estimate? This seems fundamental, as no story should ever enter a sprint unless it has been estimated; and the burndown simply doesn't work properly with a null estimate (as opposed to "zero" estimate).
Hi, we just launched JJUPIN Agile https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.jjupin-agile
While it cannot prevent easily unestimated issues being added to the sprint (yet!) - at least you can prevent issue being started until sp > 0.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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