It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
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).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
JJUPIN + JJUPIN Agile offer a solution to prevent an issue being added to the sprint but this would require some custom Javascript. Anyway, we'll think about it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.