Thanks for the quick (and precise) answer ! On Jul 18, 2009, at 12:25 PM, Andrea Tomasini wrote: >> >> I have a milestone field for requirements, stories, bugs and tasks. >> I consider useful to be able : >> - to assign a Bug (not linked with any Story nor requirement) to a >> milestone (even if I dont know yet in what Sprint it will be fixed) >> - to have some Tasks linked to that bug which is not linked to >> anything > That is possible, I wouldn't consider it Scrum... but Agilo can do > it :-)
Why wouldn't you consider it Scrum? >> The problem is that when I am in my Release Backlog, if I do a >> change for example in the Sprint column (when I prepare a Sprint), >> then all my Bugs not linked with a Story and the underlying Tasks >> loose their Milestone property : >> >> * milestone: Release 1.3.2 => >> >> Is this a bug? >> Is there any workaround? > I suspect it is due to the "business rule" Sync Milestone and Sprint, > which is there to guarantee hierarchical consistency between Sprint > and Milestones assignments. You can try to disable this, you will find > it in the Admin/Plugins/Agilo, should be SprintAndMilestoneSync rule. I prefer not to remove some "business rules" I am probably using without even realizing it. >> This is extremely inconvenient since I could loose some Bugs to >> solve in the upcoming release. > Why you do not just create a Bug Backlog? And let the teams pick out > of it at the Sprint Planning meeting? This is what I did and it seems OK. This means picking items from two different places during the Sprint planning meeting (Release Backlog and Release Defect Backlog) but this is OK. Thanks again for the precious help ! Fabrice --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
