Time estimates not tracking properly?

Question

We're having some issues with Greenhopper's time tracking functions.  Specifically, we've noticed that for some versions the time estimated is listed as 0 minutes (despite every technical task in the sprint having been given an estimated time).

Moreover, we've noticed that this problem seems to be affecting "Sprint 1" specifically in each of our projects.  It's a weird coincidence.

I've seen reference to time tracking issues with GH in other places, is there a realistic fix or workaround to it?  Otherwise the time info in the system is unreliable and thus useless to us.

Ryan Belmont1 · Accepted Answer

It turns out that Greenhopper is very finicky about dates.  The issue I was experiencing stemmed from creating tasks for a sprint that had a starting date in the past - Greenhopper time tracking is set up to not add new task time estimates to existing sprints.  That's the right functionality, it just makes backdating projects difficult.  Which is intended.

Thanks all.