Hi, > When closing a sprint and transferring remaining tasks to the next > sprint, I noticed that the burndown chart of the closed sprint > suddenly showed zero hours at the end. Is this intentional? I don't > like this kind of "history rewrite." This brings up the question of > how the burndown is calculated. I suspect that it only takes the > current state into account. It would probably be more correct to take > the ticket_change table into account. When tasks are moved to the next > sprint, their associated remaining time would be subtracted from the > burndown at that point in time. If the time of moving is after the > sprint has been closed, the burndown for that sprint would not change.
Indeed if tasks / stories are moved to a new sprint they are not anymore counted for the old sprint. We didn't get around to implement this completely, mostly because this simple solution works for now and we wanted to catch all the edge-cases, so we can get all the linking right within the ticket-model that trac provides (which is sadly a bit simplistic for what we'd need here). HTH -- Mit freundlichen Grüßen Martin Häcker Consultant agile42 GmbH www.agile42.com Grünberger Str. 54 10245 Berlin, Germany Office: +49 30 2005 3958 Fax: +49 30 2007 8274 Amtsgericht Charlottenburg: HRB 111402 CEO Marion Eickmann --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo?hl=en -~----------~----~----~----~------~----~------~--~---
