Am 07.04.2010 14:12, schrieb Radha:
Thus, the user stories in this case, would boil down into requirements
for product1 and product2. The requirements then are further broken
down into tasks. Thus, the links we intend to configure in agilo are
as follows.
User Stories -> Requirements
Requirements -> Tasks
Bug -> Task
Ok, that's a bit different from the agile42 approach:
We use 'requirements' as a problem description from a user's point of
view. The user stories are solutions to these requirements (you might
have multiple user stories to solve one problem).
This is done so you can on problems and only think about details if a
problem is important enough (lean thinking).
As per the default linking in agilo (User Story -> Task), when a user
story is created, a referenced task can be created from within the
'edit' tab of the user story.
However, when I change the links and when I create a user story, the
user story still has a section to create a reference task, and not a
requirement.
Is this a bug in agilo?
Regardless of my comments above, you should see 'create a referenced
user story' if you configure it correctly. Can you show us the
agilo-link section from your trac.ini?
fs
--
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
