Dear Customers,

After comparing this feature request against the known report JSWCLOUD-9167 we realised that both are addressing the same scenario. Since we consider JSWCLOUD-9167 the main point of entry for this scenario, we will be closing this request now and will ask you to cast your votes in the original request so we can measure the impact and interest more accurately. If you believe that this has been done in error please raise a Support request at support.atlassian.com and we will endeavour to address it.

Cheers,

Belto
Cloud Support Engineer | Amsterdam

Feature Not available since this November 2015. Does it mean it will never be available?!

Just add a checkbox to allow roll up to parent story.
If people don't want to use this feature they can leave it unchecked.

Couldn't agree more! 

+1

Agreed.  We need ability to estimate time in each sub-task, then have the time estimate roll-up to the story level and time remaining in the story then get updated from the work log and estimate of each sub-task.

Must to have feature. 

An essential Feature which will help in managing the Team's work load.

Crucial feature.  What's the point of having estimates in sub-tasks, if you can't see the total time rolled up in the story?

Needed badly. Just do it! What are you waiting for? Is there some work around that is causing deferral.

This is a much needed feature as this will fix a major gap in the product. It is incomplete without time rolling up. 

This feature is essential for detailed tracking for teams tracking sprint deliverables using sub tasks. The sub tasks estimates were rolling up for us until we did the upgrade to 8.3 version and after that Jira stopped rolling up the estimates/hours logged at the sub task level. All settings are same including Time tracking checked and include sub tasks at story level but it doesn't work. Since hours are not rolling up to the story level, some of the gadgets that Atlassian provides cannot be used like the sprint burn down, sprint health gadgets as they use the estimates from the story. Currently since the sub task estimates are not rolling up, the estimates in story are blank. It would be very helpful to get this feature back so teams can utilise the full Jira product.

I am amazed this feature request has too few votes. May be the ones voting these are doing something wrong and should work in another direction? In my opinion, tihs feature is very trivial, was one of the first features I looked for when start working with Jira and planning sprints.

+1

Hi guys,

This would be a great feature to have. Many of our IT project teams want to start utilizing the Time Tracking feature Jira has but it seems like we are running into the problem with the estimation field at the database level is not filled with the sum of the sub-tasks from those issues that were estimated at the Sub-Task level. I put in ticket PSCLOUD-27170 explaining our problem in greater detail. It's great that the sub-task estimates roll up to the Story level, but if that isn't visible on the Backlog view bubble to be utilized for Sprint Planning I'm not sure how much value there is. I see this suggestion has been open for 3+ years, but it really would be a great feature to have!

Hi, So we can't see what we need in the backlog because the estimations for subtasks are not shown. 
The only workaround is to go one step higher and work with epics and stories instead of stories and sub-tasks. But this way we have epics for the sprint. Pretty inconvenient Atlassian.