Start sprint: Tasks un-estimated

[arcotek]

Hi,

When I go to start a sprint, I get a warning message that items are not estimated:

Issues X-1, Y-2 Z-3 and n others do not have a value for the 'Estimate' field. Values entered after the start of the sprint will be treated as scope change.

The aforementioned issues are all sub-tasks.

In my sprint board's Backlog view, I cannot see any sub-tasks. The filter is set to "Type: All". If I change it to "All Sub-Task Issue Types" then I see nothing in the Backlog.

I know I can start the sprint and then size the sub-tasks but as the message says, this will cause scope-creep. What is the proper way of doing this?

How do I size/estimate sub-tasks before starting the sprint or stop the warning message?

There are several other questions on the subject of sub-task inclusion, but not one of them actually says how to do it or relates to my issue.

I've found this article: https://confluence.atlassian.com/jirakb/start-sprint-warning-792311695.html

However, it is from 2016 so probably out of date.

I'll assume "Issue Type Global" is set in filters - which doesn't exist.

I'm only a project admin so I have no access to "Custom fields".

It looks like a bug that Atlassian can't be bothered to fix: https://jira.atlassian.com/browse/JSWCLOUD-15908

TIA

[Nic Brough -Adaptavist-]

This sounds like you may by using a numeric field for estimating the sprint, and have given that field a context for sub-tasks.

Sprint estimates should not be put on sub-tasks, so I'd recommend changing the field context from "global" to "only for standard types"