We are currently using "original time estimate" instead of "story points" and want to use time estimates for story points but are only allowed to input the estimates once the sprint starts. In addition, when we start the sprint, a notification pops up saying that x number of issues have not been estimed (the number of sub tasks). Then when we add them after it is tedious and are treated as scope changes.
How can we allow time estimates for sub tasks in the backlog before the sprint begins?
My apologies, I missed the "sub" in sub-task in the question
That means the "time tracking" field is not on the "create" screen for the sub-tasks.
This is actually the default, and it's broadly correct. You are opening a can of worms if you try to estimate on sub-tasks, and that's why it's not defaulted. Stick to estimates at story/issue/task level.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs