Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,367,227
Community Members
 
Community Events
168
Community Groups

What's best practice for time remaining on task after done?

Should you leave the time remaining as a way to compare with the original estimate or zero it out at the point of Done?

2 answers

2 accepted

1 vote
Answer accepted

You should leave the original estimate as it is. If you are using additional apps such as Tempo Budgets for example, you can compare your actual versus original estimate after delivering a large initiative or program of work for example.

Thank you!  I concur.  

Like Bhushan Nagaraj likes this
0 votes
Answer accepted

In most cases, you should leave it alone.  Setting it to 0 destroys the information around your estimates not being perfect (which is natural, humans won't get it right every time - but if you don't keep a measure of it, you have no way to improve), and messes up some reporting that some people find quite informative.  There's no benefit to setting it to 0.

Thank you.  That was my thinking as well.  If you zero it out, you lose the Actuals to Originals measure to learn from.

Like Bhushan Nagaraj likes this

Does this mean anything that is DONE is no longer adding any unused hours to TIME REMAINING?

No, it will still do that.  But no one should be changing issues that are done.  It makes no sense to log work against issues that are complete and need no more attention.

Thanks. What would be the best way to not see unused time for completed tasks in a burndown chart then?Screenshot 2022-08-22 190547.png

Nothing.

Burndown measures what you saiid you would do against what you did.  There's no looking at partial completions.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events