Hi Shikarishambu This is how it currently works in agilo. At the top of the hierarchy you have the requirement, then user story and finally the Task - which is the lowest level and most detailed piece of work.
However you can configure the links to include the ability to link bugs with Tasks and User Stories through the administration section. There is a configuration area called 'Links'. This is where you can configure the links and what data is copied over when creating a linked ticket and what information you want to show on the parent ticket as a summary of the child. It's fairly intuitive to set up. If you get stuck, I can give you some examples. Iain Sent from my BlackBerry® wireless device -----Original Message----- From: shikarishambu <[email protected]> Date: Thu, 15 Oct 2009 19:27:07 To: Agilo for Scrum<[email protected]> Subject: [Agilo for Scrum] User Story vs Requirements difference, linking Tasks and Bugs to them Hi, How does Agilo differentiate between User story and Requirements? Is it better to use one over the other? If yes, which one and why? Presonally, I prefer to follow this Hierarchy - Rquirements > User Story > Bugs > Tasks - i.e. Requirements can have user sotries, bugs, tasks associated to it. This brings me to the other question I had - is there a way to link these in Agilo. Thanks --~--~---------~--~----~------------~-------~--~----~ Follow Agilo on Twitter: http://twitter.com/agiloforscrum ----- 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 -~----------~----~----~----~------~----~------~--~---
