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; } } }

Is there a way to do sub-task estimation rollup?

Chris Tooley2

We don't do any estimates based on time. All of our estimates/actuals are based on Story Points. So, when we start grooming our backlog we estimate all of our Story issues with a Story Point value. As those Stories get put into a Sprint we do task breakout. To accurately reflect partially completed Stories we assign Story Point values to the Sub-Task issues. The problem with this is that in the Chart Board and various Dashboard graphs, we can either have sizes on the Sub-Tasks or Stories, but not both due to cumulative rollup, but as far as I can find, the Rapidboard doesn't do that.

Any hints?

Accepted answers

cgauterio

Hi Chris,

You are correct, the sub-tasks (or their estimations) are not displayed on the Rapid Board, plan mode specially.

There is an improvement request regarding it being tracked at GHS-5614. Please add yourself as a watcher to be notified of future updates.

Cheers,

Clarissa Gautério

Atlassian Support

All comments

cgauterio

Hi Chris,

You are correct, the sub-tasks (or their estimations) are not displayed on the Rapid Board, plan mode specially.

There is an improvement request regarding it being tracked at GHS-5614. Please add yourself as a watcher to be notified of future updates.

Cheers,

Clarissa Gautério

Atlassian Support

Renjith Pillai

Probably it's a concept issue here, as story points are at story level and technical tasks are estimated in hours during the sprint planning. This is the reason why this aggregation is not done. At the same time, if estimation is based on Orginal estimate, the sum of the values of the estimate is shown in the Detail view of the issue.

sclowes

Hi Chris,

There's not currently an easy way to model partial burndown of Story Points. The easiest alternative would be to use hours where 1h = 1point. You can then do what you're looking to do.

Thanks,
Shaun

Ivar

We've been working hard for years to get away from the use of hours. You yourself state in the blog that

A story point approach based on original estimates can deliver the answers to these questions without the anxiety around ‘accuracy’ that teams feel when asked to estimate in hours.

So we've been estimating sub-tasks in story points. Now you want us to revert to hours again?

https://answers.atlassian.com/questions/203746/rapid-board-story-points-and-sub-tasks-aggregate-estimates-up

John Gill

Why can't you up-vote replies! If I could Ivar gets my up-vote!

Welcome!

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

Quick Links

Find more posts tagged with

jira-software