There is a misleading disconnect between JIRA and JIRA Software.
JIRA has a convenient panel that displays the estimates and worklogs from sub-tasks on a parent issue, and provides a couple of functions for summing them up in searches and so-on.
JIRA Software does not expect you to estimate at the sub-task level and does not roll up any data at all. The story's estimate is the estimate for that story, not the sub-tasks.
This is frustrating for a lot of us. There's several ways to implement "estimate on sub-task" and they're incompatible with each other, so it feels like Atlassian is ducking the question by saying "don't estimate on sub-tasks.
Hi all.
200% agree with you guys. This just doesn't make sense.
It is so handy to check the SPRINT tasks on the BACKLOG view, BUT so weird (and misleading) to see 'Estimate' value at zero while you made the effort of break-down the original TASK in smaller tasks with ESTIMATE time for each of them, in order to be able to estimate the main original TASK properly (because... that's the purpose of beaking down a task in smaller ones !!...).
Atlassian must provide us with an option to make this addition automatically in this view.
Hoping this will be heard.
Thxs in advance Atlassian.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is not clear why Atlassian chooses to tell stories instead of fixing this bug when it is clear to everyone that it is a bug
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.