I second this a s a defect.... Release backlogs are not making any
sense really, I have them configured as it is recommended and a mix of
other release's Users Stories appear in it. I'm really not in favor of
"unassigned User Stories are visible too", it just adds confusion.
Please can we get a patch or at least tell me what to change?

On Aug 6, 4:44 pm, rstacy <[email protected]> wrote:
> I just deployed the latest agilo release which was released yesterday,
> and I still have this issue.  Do I still need to get the patches or
> should those have been included in the latest release?
>
> On Aug 5, 9:49 am, rstacy <[email protected]> wrote:> Where do I get the 
> patches?
>
> > On Aug 5, 4:47 am, Andrea Tomasini <[email protected]>
> > wrote:
>
> > > On 4 Aug, 2009, at 23:48 , rstacy wrote:
>
> > > Hi Stacy,
>
> > > > 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.
>
> > > Basically only no tasks :-) The question is which of these tickets  
> > > explicitly has a Milestone assignments and what is the linking  
> > > structure that you put in place :-)
>
> > > > 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.
>
> > > So you have stories planned for Milestones? Normally we use the  
> > > Requirement as container of the value and than "wishes" for the  
> > > Product Owners for a Release plan, than all the linked stories, which  
> > > have not been planned for a sprint not belonging to the current  
> > > release, will appear automagically in the Release Backlog... So it is  
> > > normally not needed to plan a release at that level of details, you  
> > > will also have the risk that the team is feeling pushed, rather than  
> > > allowed to pull of the backlog ;-)
>
> > > Related to Bugs, they are also normally planned for a Sprint, and not  
> > > for a Milestone, and typically they are not "valuable" in the meaning  
> > > that they eventually have some "retainment" value that is not what a  
> > > Product Owner wants to plan for a Release, it is more the cost he and  
> > > the Development Team will have to bear, for not having done the things  
> > > right in the first place :-D
>
> > > > 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.
>
> > > This is really strange... I mean boths:
> > > 1) Requirements without a milestone should only appear in a "global"  
> > > backlog, and not in a scoped one, by definition, so they should appear  
> > > in the Product Backlog and not in the Release Backlog.
> > > 2) The fact that you see fields double is also strange... do you see  
> > > them in the ticket detail view or you see them as multiple columns in  
> > > the backlog? In the first case, you may check to have the right  
> > > version of template installed (go to Admin/Agilo/General and press  
> > > save) and also to have a version of Genshi <= 0.5.1, which is the  
> > > latest stable. In the development version there are bugs related to  
> > > the usage of py:match, that causes duplication of content blocks, for  
> > > which we already submitted patches, but have not yet been integrated :-)
>
> > > > Thanks for any help that you can provide,
>
> > > HTH
>
> > > > Rob
>
> > > ANdreaT- Hide quoted text -
>
> > - Show quoted text -
>
>

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