Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Warning of Estimate Field for stories while creating a sprint

I have created screen schemes for epics and stories, where I haven't added estimated field.

This field was automatically calculated from the sub tasks automatically.

But when I am trying to start a sprint, it is showing a warning as below:

Issues SAMDOC-10 and SAMDOC-8 do not have a value for the 'Estimate' field. Values entered after the start of the sprint will be treated as scope change.

How to overcome the above  warning?




2 answers

0 votes

Enter the estimates on the stories.  Scrum only looks at the Story estimates because there is no partially done concept - an issue is either complete (so it can be burned down) or it is not (so it's open and can't count).  Sub-tasks are irrelevant in burn-down, so Jira ignores them.

(There are uses for estimates at sub-task levels and several ways to approach handling them.  But because coding for all the possibilities is a big task, and wouldn't change burn-down, Atlassian have chosen to simply not do it.  So you need the estimates on the Story level)

It seems that this behaviour has changed with the last upgrade (8.13.2). We now do get a warning if subtasks are not estimated.

Anyone else suffering from this?

Your "Story Point" configuration might be pointing to Global issues or it is associated to sub-tasks. Associate this field only to issues where you use it, this will remove the warning msg.

More info here:

I am having the same issue. If I open a sprint with no sub-tasks under my stories I do not get an error message. If I do have sub-tasks, whether they have estimates or not, I get an error message that states the particular sub-task under the story (which is sized) does not have a value for the Estimate field. Values entered after the start of the spring will be treated as scope change - In the configuration of the board under Estimation I have the Statistic as Story Points and Time Tracking as None. - any thoughts to help me on this? 

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