Sub tasks do not have a value for the 'Estimate' field error while starting the sprint

[Aswani kumari]

I am unable to start  the sprint, getting the below error.

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

Includes issue(s) currently hidden by a Quick Filter or the Instant Filter.

Please help

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

One of your admins has set the estimate field as mandatory, but not added it to the create screen.

This is not a good thing to do - you should not be putting (sprint) estimates on sub-tasks unless you have automated a system to calculate them up to the sprint items in a way that won't break all your reporting (most people don't understand the initial double counting, but then try to implement a scheme that ruins your team's ability to be Agile)

So, the best thing you can do for now is removing the field from sub-tasks and make it optional.

Then you can look at how you really want to do estimates.

[John Funk]

Hi Awani - Welcome to the Atlassian Community!

it sounds like someone has made that field mandatory for sub tasks. you should check the field configuration for the sub task issue type to see if that is the case.