The Issues showing are all Stories, that have sub-tasks with Estimates. We never put Estimates in a Story so not sure why we are seeing this warning message.
I was able to start the Sprint after going back to each story and entering a "zero" (0) into each Estimate field instead of leaving it blank. I have always been able to leave that field empty before, but this time, for some reason, it did not like that field being blank. Any ideas?
Thank you to the information Celia!!
Some of our users too are facing a similar issue. I will ask them to try this workaround until we upgrade the JIRA Agile and provide feedback.
https://confluence.atlassian.com/display/JIRAKB/Scope+Change+Warning
It looks like you're new here. Sign in or register to get started.