nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Subtask estimate not rolling up to parent

amit agrawal_p0e6za

Scenario:

1) I have created Story with Original Estimate of 4w

2) I have created Subtask 1 Original Estimate of 2w

3) I have created Subtask 2 Original Estimate of 2w

4) I log work on Subtask1 for 1 w

5) Subtask1 Remaining Estimate shows 1w which is correct

6) Story Remaining Estimate still shows 4w

Please suggest why log work is not rolling up to Parent Story.

Accepted answers

Nic Brough -Adaptavist-

Could you explain where you are looking for the rolled up values? Have you got the "include sub-tasks" box ticked in the panel?

All comments

Simple Tyler

Hey Amit,

The issue is likely that you put an Original Estimate on the Story.

If you remove the Original Estimate from the Story and let the values roll up from the Sub-Tasks they should be reflected properly.

Hope this helps,

Tyler

amit agrawal_p0e6za

I Tried all possible scenarios but it did not work.

I spent 4 hours but unsucessful.

I am not sure whether it is supported.

Any help will be appreciated. I

Nic Brough -Adaptavist-

Could you explain where you are looking for the rolled up values? Have you got the "include sub-tasks" box ticked in the panel?

amit agrawal_p0e6za

At Parent Level issue.

Remaining Estimate.png

amit agrawal_p0e6za

What you are referring to Time Tracking. Which is not what i am looking.

In my JIRA dashboard using filter result, I would like to show how much Progress I am making on Issue. Currently it is reflecting 0% as Remaining Estimate is not rolling up from Subtask Log work.

Nic Brough -Adaptavist-

I think you have misunderstood. Time tracking and time estimation are the same thing. A parent issue has a panel that shows the time tracking, with a flag to tell it to include sub-tasks or not.

Have another look at the available fields; the ones like original estimate, work logged etc report only on the current issue. Go to the bottom of the list of fields and you will see Σ fields that have the same name. Those mean "show data current issue and sub-tasks (if any)". Those should do what you need in a filter result gadget.

Ignacio Pulgar

This seems to be an issue related to the new Jira issue view:

https://jira.atlassian.com/browse/JSWCLOUD-16878

Ivan Tkachenko

Hi all, this is how I resolved this issue:

Board Settings -> Card layout -> Choose 'Σ Original Estimate' / 'Σ Remaining Estimate'

Hope this will be helpful!

eliran zur

works perfect!

Thanks

Matthew Grabowski

This is incorrect. Once an original estimate has been put on a story, sub-tasks will never again roll up to it, regardless of whether the original estimate is removed.

Seems like a Jira bug.

Nic Brough -Adaptavist-

Yes they do. Just flip the "include subtasks" flag.

Judy Colonero_tkrrzy

Logged my comment, we need this functionality.

Kevin Cassman

I agree. We really need this. It is creating a lot of manual work for me and team because of this.

Matthew Grabowski

I really hope this isn't a case of "not a new bug, will never ever fix"

unknown

Hi, I have some issue related to Remaining time estimate.

1. The sprint has been created by some user.
2. The sprint contains defects and stories
3. Remaining time estimate has been provided in sub-tasks during issue creation, which is visible in parent issue's time tracking. (If we remove Include sub-tasks, the Time tracking data will be invisible because it was coming from child tasks).
4. I added few details in active sprint's backlog, to view time estimates (i.e., Σ Original Estimate and Σ Remaining Estimate). So I can view total time estimate and total remaining time. So data is fine here.
5. When I check workload by assignee in sprint's backlog (by pressing three dots), I see Remaining estimate and Remaining time estimate based on assignee. Which is zero in all cases... The workload feature addition details provided by Attlassian is here. https://jira.atlassian.com/browse/JSWSERVER-11177?error=login_required&error_description=Login+required&state=cd4a5d3e-674a-4ab9-9569-e0d09497f9d4
6. This Remaining Time estimate is zero for all the issues where time is being taken down from sub-tasks, while it is giving value for those were estimate time has been added for paresnt task.

7. When I see burndown report for that sprint, it takes the same figures (as in asignee workload) .Why Remaining time estimate is not being read properly when Σ Remaining Estimate per issue is present.

****It is the case that sprint does not take sub-task's time estimate when sprint is created?Because when sub-tasks are showing correct estimate after work-logs are added in later point of time, why the same remaining estimate is being recorded in burndown when sprint was first created?

Please provide your opinion based on your work exp.

Thanks

Iain Brown_ezetls

I can confirm I have exactly the same issue described above by Pooja. The remaining estimate is zero in the workload by assignee, when this value is determined by sub tasks only. Observed on multiple projects. Cards have the estimate items added as in 4. above.

To further show the behaviour , if I goto a story that has various estimated sub tasks, and add an original estimate at the story level, then ONLY this new value appears on the workload by assignee table, not the total estimate including sub tasks.

Jira cloud 8.5.5

Iain Brown_ezetls

As a followup I have resolved the observation above.

In this case the scrum board filter query excluded sub tasks issue types. When this was changed to include sub tasks then the estimates by assignee shows as expected.

I then added a quick filter to exclude the subtask issuetype when required.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-core

jira-core-server