We have used vanilla trac for managing tickets up until now. Now we want to convert these into agilo-managed tickets, mainly to improve our planning.
The first observation is that we have used milestones as a way to group related tickets. Other milestones would be releases, and when we decide what features go into each release, we reassign the milestone for those tickets. Roughly speaking, some milestones would then be comparable to a User Story, at least when doing the initial conversion, and our old tickets would either translate into Tasks or Bugs. So I was thinking of doing this, and then gradually fill in the product backlog by adding Requirements and additional User Stories as needed, moving, sorting and re-prioritizing tasks accordingly. What I seem to be missing in Agilo is a simple way to split User Stories, and to move Tasks between User Stories. Even move User Stories between Requirements could be useful when refining requirements. My questions are thus: Is there such a refactoring feature somewhere, but I don't see it? Or is it planned? How have others managed their transition from traditional trac? What's the official guidelines for this? Best Regards, Mats -- 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
