Stories time estimate field is incorrect when adding Sub-Tasks (Sub tasks are correctly inputted)

[GameDev]

Hi

We use the estimate field as the [work begins] and [work ends] tab is turned off as its a little complicated in our first ever Jira classic move over (we have been using next gen for 9 months). Slowly the benefits of jira inc dashboards is filtering through to us.

At the moment we have a big problem whereby the main stories time estimate is all wrong, but the sub tasks estimates have been inputted correctly. We use 0.5h as the minimum for a task (ie 30minutes) and it goes to 1d (for 1 day) and 5d (goes to 1week) by itself in the "time estimate" field which is good.

So why doesnt the story accumulate all the sub tasks time estimates and then update it correctly in its own "time tracking" log?

Any solutions gratefully received.

Thank you.

[Nic Brough -Adaptavist- · Accepted solution]

Because the work is being done on the sub-tasks.  You don't want to double-log work on a sub-task and its parent.

The estimates and work logged are summed up for display and reporting though.  Go to the parent issue and look at the estimate area - you will see a flag for "include sub-tasks".

Let's imagine a really simple case:

• ABC-123 - parent issue, 5d estimate, work logged 1d
  • ABC-125 - subtask of ABC-123, 1d estimate, work logged 2d
  • ABC-128 - subtask of ABC-123, 3d estimate, work logged 3d

With the flag set to include, you'll see ABC-123 display a 9d estimate, 6d logged.  Turn it off, it'll show 5d estimate and 1d logged.  You'll notice that the estimates and work logs on sub-tasks do NOT affest the estimate or work logs on the parent, they're separate things.

If you go to the issue navigator, you can also see these displays including sub-tasks in the fields that start their names with a  ∑ character

[GameDev]

Thanks Nick, I'll chase this up when i get time and go through that guide you put.