I have an assortment of User Stories, Requirements, and Bugs.  One
note is I have configured the backlog to allow Requirement, User
Story, and Bug ticket types.

For instance, I have one User Story that is closed and assigned to a
previous milestone.  An interesting note is when I bring up the User
Story it shows the reported by and owner fields twice on the view only
screen.

I have requirements that have milestone of n.a. and they are showing
up in the release backlog as well.  The same with bugs.  All of my
tickets seem to show the reported by, and owner fields twice on the
view screen.

Thanks for any help that you can provide,
Rob

On Aug 4, 3:16 pm, Andrea Tomasini <[email protected]>
wrote:
> On 4 Aug, 2009, at 20:18 , rstacy wrote:
>
> Hi Stacy,
>
> > I have recently established a release backlog.  I have set the scope
> > of the backlog to milestone, and enabled strict setting.  However,
> > when I click the view release backlog button, I see tickets that are
> > not scheduled for the release.  Many of the tickets in the backlog are
> > scheduled for past releases or have a value of N.A.  Am I missing
> > something?
>
> Probably not... in that backlog will appear all the Requirements that  
> have been planned for that milestone, and with them all the User  
> Stories connected to the requirement, that are not explicitly planned  
> for Sprints outside of that milestone, this is the idea at least.
>
> So which kind of ticket that shouldn't be there do you see?
>
> We need a bit more of information to help you ;-)
>
> Best
> ANdreaT
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to