Time tracking - remaining estimate displays wrong hours

[lisa.skantze]

Hello!

I have a problem with Time Tracking.

I have a story with sub-tasks. On story level I have the original time estimate of 100 hours.

In the sub-tasks I have logged time that exceeds the 100 hours by 29 hours.

Logged time says: 129 hours

But remaining time says: 104 hours (see screenshot added)

There are no estimates added to the sub-tasks - there is only the one estimate for the user story. 

Is there something wrong with the cloud version? Or am I doing something wrong? Why does it say that the time remaining is 104h?

The percentage of the graphs appear correct but the numbers are wrong.

Is anyone else experiencing this?

Kind regards,

Lisa

Providing screenshots of what it looks like:

[Warren]

Hi

It would be useful for you to untick Include sub-tasks and give us another screenshot. I have an idea, but would rather wait until I see the results of the next screenshot

[lisa.skantze]

Hi Warren,

Here you go!

[Warren]

Hi Lisa

With respect to your screenshot with sub-tasks test1, test2 and test3, what you're seeing there is correct.

test3 only has 5hrs logged of a 10hr task, but it is complete (100%). When you complete a task, Jira automatically sets the remaining time to 0, because you're not going to do any more work on it - it's complete. So the only remaining time on the story is the 6hrs for test1. This all makes sense and is correct.

[lisa.skantze]

Hi Warren, 

But it is not complete - I just logged 5 hours as I did 4 hours on sub-task 1. Why is it different. I think sub-task 1 behaved correct - I have 6 hours left. However Sub-task 3 - where I added 5 hours - should say 5 hours remaining. Right?

[Warren]

Hi Lisa

test3 is showing 100%. Can you give a screenshot of the time tracking within test3?

[lisa.skantze]

[Warren]

So the remaining is 0, which implies everything is correct. But ... how did remaining get to 0? You may need to check the History tab of test3 to see what's happened. I can't know unless you show me the History but I suspect that possibly you've set the remaining time to 0, without meaning to

[lisa.skantze]

Hi Warren,

Ok, attaching history screenshot.

The only thing I did was add 5 hours to the work log. I would expect 5 hours to remain.

//Lisa

[Warren]

Okay, so I can see where you've gone wrong. If you set the Original Estimate, but leave the Remaining Estimate blank, it populates the Remaining with the Original value.

What you had done was to set both estimates to 0 (3rd row), then you changed the Original to 10h (the second last row). At that point, your Remaining would still have been 0. Then you logged 5h, and Remaining is still 0.

So, when you create a sub-task, add a value to Original Estimate (say 10h), but leave Remaining blank; once created, you'll see that Remaining is now also 10h. As you log time, the Remaining will reduce until 0, which is what you are expecting.

I hope that this is clear

[lisa.skantze]

Hi Warren,

Yes, it is clear now. Thank you for taking the time to explain.

I have another question for you if that is ok?

If I have added an estimate to the parent story - say 60 hours.

If I add sub-tasks and log time against these should they not deduct the time from the parent task estimate?

Kind regards,

Lisa

[Tyler Brown]

Hey Lisa,

The issue is likely that you placed the Original Estimate on your Story and not on your Sub-Tasks.

Time logged against the Sub-Tasks won't burn down time on the parent Story.

Tyler

[lisa.skantze]

Ok - so there should be no time estimate on the story and only on the sub tasks?

[lisa.skantze]

Are you sure this is the way it works?

[lisa.skantze]

Hi Tyler,

I just tried to add one story without any time estimate.

I added three subtasks with estimate of 10 hours each.

I logged:

Sub-task 1 - 4h

Sub-task2 - 10h

Sub-task3 - 5h

19 hours logged. Still remaining time says 6 hours? This should be 11 hours. 

Providing screenshot.

Thankful for any input on this. :)

Regards,

Lisa