On Oct 5, 9:24 am, Martin Häcker <[email protected]> wrote:
> > I just started evaluating Agilo for a large existing project and
> > really like it so far. It looks like it may work for us. I'd like to
> > report a bug in the Sprint page, however. The following calculations
> > seem to be made for planned, open, and closed tickets:
>
> > 1. Closed tickets are actually closed tickets for the current sprint.
> > This seems to be calculated correctly.
> > 2. Planned tickets seem to be calculated as any tickets that aren't
> > closed. Was this intended to be new tickets?
> > 3. Open tickets is calculated as the difference between the closed
> > tickets and the planned tickets, which doesn't seem to be a valid
> > calculation. Was the intent for this to be any tickets that aren't new
> > and aren't closed?
>
> > An example:
>
> > I have 8 tickets, 5 are closed and 3 are in any state other than
> > closed. The Sprint page will say that I have 3 planned tickets, -2
> > open tickets, and 5 closed tickets.
>
> We are not completely sure yet, this is definitely a bug in the
> calculation and we plan to get it fixed for the next release, however we
> weren't able to reliably reproduce it.
>
> Are you able to do that? If so, we'd love to get more information about
> how you did it.
>
> Best Regards,
> --
> Martin Häcker
> Consultant
>
> agile42 GmbHwww.agile42.com
> Grünberger Str. 54
> 10245 Berlin, Germany
>
> Office: +49 30 2005 3958
> Fax: +49 30 2007 8274
>
> Amtsgericht Charlottenburg: HRB 111402
> CEO Marion Eickmann
Thanks, Martin. Yes, I can reproduce the problem any time I have more
closed tickets than open tickets. I think that the calculations for
planned and in-progress tickets isn't correct.
It looks like the GetTicketsStatisticsCommand class is returning two
numbers:
1. nr_planned = The number of open tickets for a given sprint -- this
is anything that's not status "closed".
2. nr_closed = The number of closed tickets for a given sprint --
anything that is status "closed".
The calculation on the sprint page uses those numbers for these
calculations, however:
1. The number of "closed" tickets is correct.
2. The number of "planned" tickets is all open tickets
3. The number of "in-progress" tickets is the difference between
nr_planned and nr_closed. I don't think this is a correct calculation,
because nr_planned and nr_closed aren't really related. For instance,
if I have 8 tickets, and have closed 5 of them, I'll get -2, as in my
example above. Even if I've closed only one ticket, it will say that I
have 7 planned, 6 open and 1 closed. But the 6 open tickets doesn't
match the real state.
Was the intent to separate new (planned), in-progress, and closed
tickets? If so, then the GetTicketsStatisticsCommand could be changed
so that it returns the number of new tickets (nr_planned), the number
of open tickets that aren't new (nr_inprogress or something like
that), and the number of closed tickets (nr_closed).
Thanks again!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
