It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Epic to story to sub task time estimating and roll up doesn't really work!

We are trying to use SCRUM boards to manage progress on a sprint based project.

We have a number of epics. Each epic is decomposed into a set of user stories, and each story is decomposed into a number of sub tasks.

The first problem is that time logging at a sub task level isn't registered as progress at the user story level. I've seen a few postings here that say that this is how the product is designed to work, but its plainly counter intuitive to not support roll up of sub task estimates and progress.

Elsewhere I've seen suggestions that the way to address this is to remove the estimates from the story level, but in doing so this undermines aggregate estimates at the epic level. Hence, if I remove user story level estimates there are no estimates available at an epic level - again this is plainly counter intuitive.

My inference is that you already have the correct aggregation logic for estimates and remaining time delivered for how 'epic' stories work. Why can't the same logic be introducted for user stories and sub tasks??

My suggestion would be to:

* Add a project level configuration option that allows parent issue time estimates and remaining time values to be drawn from subordinate issues where such child issue data exists

* Alternatively add some extra fields at an issue level for storing the aggregate child issue time estimates and remaining time values.

4 answers

@Atlassian - Could someone please share a method to see the total estimated hours for (child) stories and sub-tasks rolled up to the (parent) Epic issue? Or share if there is a change on the JIRA and/or JIRA Agile roadmap to enable it? 


I also find the current situation confusing with what gets rolled up and what not.


The new Portfolio Live plans for example seems to do what we would expect:

- Epic estimate shown as (epic original estimate + linked story original estimate + linked story subtask estimates).

  • Possible bug here: epic subtask estimate doesn't get rolled up.


But in JIRA Software the epic displays as (epic original estimate + epic subtask estimates) with linked stories estimates not taken into account.


So if I want my JIRA Software Epic estimates to be rolled up correctly I would be forced to use Epics + subtasks. But then my JIRA Portfolio live plan will display incorrectly. 

Or perhaps I should then not use Epics and only use stories and subtasks in JIRA Software as they roll up as expected in JIRA Software and Portfolio.

I am having the exact same issue. Please let me know if a resolution was found for this problem. 

same here. i'd highly appreciate to have a solution working with portfolio AND the jira view

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Portfolio for Jira

Program managers, we need your help! We want to learn about how you plan work for a team of teams

Hi community members, My name is Erika and I’m a product manager at Atlassian. We’re currently investigating how teams are planning work at the program level. We understand that every team in a tea...

85 views 0 4
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you