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

How can I add original estimate to sub-tasks, so the estimate for the story is the sum of those?

Bruno Ritagliat

Currently the only way I found to enter an estimate in a sub-task is to log some work (mandatory field in time tracker) and then set the remaining manually in the same screen. But actually I need to do that in a planning stage when I don't log work (hours) yet.

And also, when I log work in the sub-tasks, I would like to have them deducted from the remaining estimate of both the sub-task and the user story.

The main purpose of this is to have an accurate burndown chart in hours.

Is it possible to configure the tool to get this scenario? If not, could you please recomend a workaround for it?

Thanks!

Accepted answers

All comments

cgauterio

Hi Bruno,

Unfortunately no, the Planning of Agile boards only takes under consideration the main tasks. There's an open suggestion regarding sub-tasks estimations showing up on the Backlog section of the boards being tracked at: https://jira.atlassian.com/browse/GHS-5614

Please add yourself as a watcher to be notified of future updates.

Cheers,

Clarissa.

Bruno Ritagliat

Hi Clarissa,

Thanks for your reply.

I understand the issue.

However, I think I finally found a workaround. Now I’m getting the sum of the original estimate (in hours) of the sub taks as the original estimate (in hours) of the user story. This is for time tracking and burndown chart purposes only.

For velocity purposes, I’m entering story points at the user story level.

At a planning stage it looks fine. I hope it works when I have to monitor the burndown chart (in hours) during our first sprint.

Regards,

Abhishek Chandel

Hi Bruno,

What was the work around. I also want to do the same thing.

Bruno Ritagliat

Hi Abhishek,

First, you need to add Work On Issues permissions to the 'Permissions Scheme'.

This will allow you to enter original estimate (in hours) at the subtask level. Then you will get the sum of the original estimate of the sub taks as the original estimate (in hours) of the user story. This is for time tracking and burndown chart purposes only.

For velocity purposes, I’m entering story points at the user story level. For this, you need to set the Estimation Statistic to Story Points.

Regards,

Abhishek Chandel

I have all these enabled but I don't see the original estimate at the sub task level. I am able to log work. For time being I am entering time spent as 1m and manually setting time remaining estimate. How do I enter original estimate at the time of planning?

Bruno Ritagliat

You need to add Work On Issues permissions to the 'Permissions Scheme'.

Shirley Jhirad

Hi,

I Have a similar scenario i would like to describe:

First, in a very initial stage im giving an estimation on the epic level in time units of weeks
Then, on the story level, in the release planning i'm estimating the stories in time units of days
Finally in the sprint planning a detailed estimation in hours

So now i'm having an issue, if i'm giving an original est. on both stories and their Sub-tasks the estimated field on the story level is updated to the sum of the story+sus-tasks estimation.

I would like to manitintain the org. est. of the story and see kind of a correct est. for the sum taken from the suc-tasks(And offcourse, all should be aggregated to the Epic level as well).

So currently to achive that i'm not updating estimates on the sub-tasks level, only using Time tracking. But i'm afraid this will affect me as i'm using the OOB reports like the burndown and velocity charts.

Any advise? @Clarissa Gauterio @Bruno Ritagliati

Thanks

Shirley

Daniel Eskenazi

This worked for me.

John Xanthopoulos

This is not working.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud