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?
Add the time tracking field to the Sub_Task create screen then.
Not sure, but I don't see any estimate field for sub tasks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Why do you say you aren't allowed to add Sub-Task estimates before a sprint starts? That's not a normal thing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't understand why you're not estimating before you go into the sprint. What have you configured that prevents it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
not sure but I don't see any estimate fields for sub tasks specifically until after the sprint starts
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.