Hey DLP,
I think I have a similar problem (see here
http://groups.google.com/group/agilo/browse_thread/thread/6ac2f541e7fd60c3)
and in both cases we're bitten by a "feature" from Agilo. Backlogs
with a "global" scope filter requirements and user stories that were
assigned a sprint OR milestone. In the case of the product backlog it
makes sense to remove requirements and user stories that are assigned
to a sprint, but when using milestones to roughly group requirements/
stories into versions (in my case the "minimal marketable product")
the mechanism is not handy at all.
I don't assign the milestones to the user stories, only to the
requirements, and as long as there are non-assigned stories in a
requirement with a milestone the requirement stays in the backlog...
that's my "workaround" for now.

Cheers,
Chris


On 30 Aug., 21:55, DLP <[email protected]> wrote:
> I've created a backlog with milestone scope.  Created a requirement
> for a particular milestone.  Created user stories for the
> requirement.  When I look at the backlog for the milestone I selected,
> I see the requirement but not the user stories.
>
> I went back to the demo provided with the installer and changed the
> demo backlog from global scope to milestone scope and selected a
> milestone for the requirement.  When I look at the backlog for that
> milestone, I see the req as well as the stories.
>
> What I deduced later is that the stories in the demo are showing up
> because they are assigned to a sprint, whereas, in my case, I haven't
> yet assigned them to a sprint.  This seems odd to me.  It seems like
> if the story is linked to a req, the the story should show up in
> whatever context the req shows up.  Otherwise, I can't see how one
> would go about ordering the stories.  Also, in order to assign the
> stories to a sprint, I either have to go search for them or I have to
> open the requirement and select each one in turn.  This defeats the
> purpose of a backlog, IMO.
>
> Perhaps I'm missing something?

-- 
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

Reply via email to