Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can i block a story from being added to a sprint if it DOES NOT have Story Points?

I don't want stories in my sprint if they have not been estimated. Is there a way to configure this?

7 answers

Personally I (as a Scrum Master) believe that people are over tools. Having the tools dictate what you should and should not do takes away social and personal responsibilities. Team members will start thinking that the tool will solve all problems and over time the team members will degenerate into tools slaves instead of highly motivated and responsible members.

I am from Scandinavia so I might be extremely biased towards individual freedom and responsibility and accountability over rules, razzia and tool enforced methods.

Reading through many of the questions and answers here it does seem that especially Asia (or people managing people from Asia) is struck by the "more rules"-concept.

So my answer is: More training. Agile Scrum is 200% about encouraging the team members to take personal stake in what they are doing rather than being treated as cattle being pushed arounf with yet another new stick called "Scrum in JiraAgile".

Encourage the team, talk about the values of Agile Scrum: Courage, Openness, Respect, Focus, Commitment

In regards to get the estimates right I suggest taking a good look at Commitment, Respect and Openness in regards to getting the sprints right.

Also do look into having a Definition of Ready and Definition of Done for the team as this will get the team to talk about exactly what the quality goals for all work is and the goal for good story preparation is.

I hope you can use this for something.

nope... wrong answer

Like Roy Powell likes this

Hi Mark,

Why don't you make the field required on the Open -> In Progress transition?

They will still be able to add the stories to a sprint but they will not be able to start them untill a value is filled in for the Story Points?

But as Kim says : it's really a team issue. Ask them why they aren't doing it? Don't they see the advantages? Is it too much work? (This is Peter the Scrum Master speaking now)

Maybe you could organize a meeting each sprint with as your only goal : give all stories a story point estimation, you can use planning poker do this more easily.

Best regards,


You can't block it but in the boards you can update the filter not to show the stories which doesn't have story points. Will that work?

I get where you're going with that... but i don't think it will work.

The idea of Sprinting means your sprint team members have commited to completing work/stories by the end of the sprint. The story points measure the teams estimate of that body of work. If there's no estimate, there can be no commitment.... so i don't want stories to be dragged into the sprint without that estimate process happening. I have several teams using JIRA/Greenhopper, so it hard to enforce right now. Any idea's ... (other than additional training!!) I'd just like to enforce it via the tool if possible.

How about setting the estimate field to be required?

That would involve a workflow change to add another status that can be transitioned to because Open -> In Progress is already in a sprint.

If the estimate is set to be required on story entry it would completely hamper entry of anything to the project, or get the project estimate count skewed completely due to lots of bogus or zero estimates being entered.

So it can be done but will have consequences.

As I understand the question the problem at hand is that sprints are created and commited to with unestimated issues. This is definitely a team issue.

how can I set estimate field as mandatory?

I've decided to create a report that will locate stories that are in sprints that do not have an estimate. With this info I can go to Scrum Masters and provide additional training.

I think you have made the right decision. Please accept an answer to close the question.

This may be an old question but I have a new solution that works for my scrum team.


In the board configuration, set the card colours depending on your chosen criteria.

For my team, I have a criteria that meets the Definition of Ready with a check that the story is not already in the active sprint.  I set the card colour to green for this.  In the backlog, all the stories that meet the DoR but are not in the current sprint are shown with a green card tab.

I also have other card colours that show what is wrong with a story; For example:  Red for no acceptance criteria.  These show the colour even when the story is in the current sprint.  Helps when looking at the sprint board to realise that something important is missing and needs to be addresses sooner rather than later,

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you