Green Hopper Remaining Time estimation question

In our way of working we use the Original Time Estimate for estimation and "Remaining Remaining Estimate and Time Spent" when calculating burndown chart. (In the configuration of the rapid board)

Then we create a Story MyStory and sub-tasks in them, and say a sub task A is estimated to 3days and a second sub task B is estimated to 1 day

First problem is that MyStory time estimation Original Estimate shows empty and remaining shows 3+1 = 4days. The logical thing would be that Original Estimate of the story would also be 3+1 = 4 days.

Second problem: We update the subtask A work log by saying that we have worked 1 day on it and then we think we are done with it so we move it to Done. Now still the remaining time estimate shows 2 days for A and 3 days for MyStory and the burndown chart shows also wrong. The correct way of handling this would be that remaining time would automatically would be set to 0 when moving the task to done and put the "remaining time" in another variable using for calculating estimation accuracy.

1 answer

Hi Keyhan,

There is a complete discussion of time estimates and tracking in GreenHopper on this blog. Shaun covers it better there than I could here, worth a read.

Thank you,
Nicholas Muldoon

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in United States

From Atlassian: Confluence Security Advisory - 2019-03-20

Atlassian released a security advisory on 3/20/2019.  The full advisory is here: In a nutshe...

13 views 0 1
View post

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you