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.
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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!
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