Prevent adding a story to a sprint if it has no Story Point estimate?

[Jim Strange]

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).

[Justin Leader]

Perhaps with custom scripting or plugin development.

[Jim Strange]

That's a bit vague - can you point to resources or something?

[Radu Dumitriu]

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.