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?
It is because your stories that are included in the sprint do not have Story Points associated with them, instead of dates now story points are a better measure to estimate efforts, Simply go to any story and in the Story Points field assign points to each story, these points can be relative i.e you can set an upper limit of 100 for example, now 100 is the estimate for your highest effort task, based on that you can assign story points to each story.
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?
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)
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.