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

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

2 answers

Perhaps with custom scripting or plugin development.

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

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 29, 2019 in Jira Software

Transforming Jira Software projects for general project management purposes

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

143 views 0 6
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you