Hey Siri, On Friday 09 July 2010, siri wrote: > Hi, I'm in my first sprint and I wonder if this is a known problem: > The actual burndown line hits zero while there are still tickets with > remaining time left in the sprint backlog. > I have trac 0.1.77 and agilo-1.3.0.3.
This should not happen. Did you change the Agilo version sometime mid- sprint? There is one limitation regarding ticket type changes. If you, for instance, plan a task for a sprint and it has a remaining time, and then you change the type to be a story (thus the remaining time disappears) -- it is not really disappearing, but still stored in the database. But this should only lead to numbers above 0 even if no tasks are left. Could you share the contents of your 'agilo_burndown_data_change' table (SELECT * FROM agilo_burndown_data_change)? Cheers Robert -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by agile42 GmbH <http://www.agile42.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
