Creating a new ticket type isn't a very interesting solution, but it is possible. Sometimes a User Story that at first is ready for development, and due a business change, needs to be splited in two. The most logic approach is to reference a User Story to another User Story.
The way I am working is, when I need to split a User Story, I create manually a reference to the old Story in the comments field (the ticket number is the link). Why is not allowed to make these references? Is it a process decision (the process in Agilo was thought not to allow this) or is a technical limitation (trac doesn't allow this)? On Mon, Sep 26, 2011 at 4:53 AM, Stefano Rago < [email protected]> wrote: > Hi Renne, > > > On 21/09/11 11:45, Renne Rocha wrote: > >> >> How do you deal with User Stories created in the beginning of the Product >> Backlog but when I do backlog grooming I discover that it should be splited >> in two User Stories instead of one? It isn't an epic because the PO believes >> that is really an INVEST Story before the grooming. >> >> The development process in my company asks me that I maintain a link >> between the artifacts created during the backlog grooming, and all file >> commited to our repositories is associated with a trac ticket. For example, >> I have US1 and I commit some files during backlog grooming to help the PO to >> understand and refine this Story, then he realized that this Story should be >> splited in US2 and US3. >> >> I need to have traceability between US1 and US2 and US3. But it is not >> possible to create link between the same type of link. >> >> Is someone working like this? How can this be solved? For now I am >> creating a comment in the new USs citing the referenced story. But there is >> a better way to do this? >> >> >> > Since, as you said, in Agilo it's not possible to reference tickets of the > same type, > one solution could be creating another ticket type, e.g. Draft, that you > can link to User Stories > afterwards. The drawback would be having to copy over the Draft data to a > User Story > if you don't create new stories out of it, since it's not possible to > change the type for > a ticket after you created it. > > Hope this helps > > Cheers > > > -- > Stefano Rago > > > -- > Follow Agilo on Twitter: > http://twitter.com/**agiloforscrum<http://twitter.com/agiloforscrum> > Please support us by reviewing and voting on: http://userstories.com/** > products/8-agilo-for-scrum<http://userstories.com/products/8-agilo-for-scrum> > http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/** > agiloforscrum <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 > Agilo Software GmbH <http://www.agiloforscrum.com>**. > > To post to this group, send email to [email protected] > To unsubscribe from this group, send an email to > agilo+unsubscribe@**googlegroups.com<agilo%[email protected]> > For more options, visit this group at > http://groups.google.com/**group/agilo<http://groups.google.com/group/agilo> > -- 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 Agilo Software GmbH <http://www.agiloforscrum.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
