Hi Sébastien,
On Thursday 17 June 2010, Sébastien Volle wrote: > You should note that the Trac instance we're using is pretty old, ie > it has undergone a lots of customization but this I don't see how it > could affect how the burndown chart is generated. While you're not using the most recent 0.11.x release, your version is not known to cause this amount of headache. In 1.3.0.1, the burndown history (i.e. remaining time before now()) is stored in the database, and not calculated on the fly. So in theory, if you see a burndown data point at 42 two days ago, it should still be there tomorrow. In previous versions, if tickets changed their type or lost some fields, they would be lost for historic burndown calculation. The exact issue that you described is not something I have heard before. I would strongly encourage you to try Agilo on a vanilla trac instance and re-add the plugins you have installed as needed. It's probably an interaction between Agilo and one of them that causes the issue, but I cannot say which one it would be -- maybe the timingandestimationplugin? Regards 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
