Discussion:
[Agilo for Trac] Story point burndown chart behaves unexpected
Marc Rawer
2013-07-16 17:02:41 UTC
Permalink
Hi,

I'm running latest version of Agilo for trac on my site and see unexpeced
behavior on the story point burndown chart so I went online to your
demo-site and tested behavior there. I created 5 new userstories
(test{1..5}) and gave them increasing storypoints (1,2,3,5,8). I assigned
each of the user stories to a user and the srpint "story_point_test2". I
set the start date to tomorrow and committed the sprint. Result:
- the number of user stories was calculated correctely to total = 5
- the start of the burndown chart was marked at 19
- the ideal burndown line started at 8
=> seems like it does not take the sum for the ideal burndown but only the
last added story?
- I changed the story point of test5 to 0 and both start points drop to 0
- I changed the story points of test 4 to 20 and the start points went up
to 20

This looks like a bug to me because it only takes the last changed story
point value instead the complet sum of storypoints into account when
setting the start of the burndown chart.

Next, when a sprint is committed it seems that you can not change
responsibility anymore. Is this wanted this way?

Thanks in advance,
Marc
--
--
Follow Agilo on Twitter: http://twitter.com/agilofortrac
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-trac
http://freshmeat.net/projects/agiloforscrum

You have received this message because you are subscribed to
the "Agilo for Trac" Google Group. This group is focused on
supporting Agilo for Trac users and is moderated by
Agilo Software GmbH <http://www.agilosoftware.com>.

To post to this group, send email to agilo-/***@public.gmane.org
To unsubscribe from this group, send an email to
agilo+unsubscribe-/***@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/agilo

---
You received this message because you are subscribed to the Google Groups "Agilo for Trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilo+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Marc Rawer
2013-07-23 13:20:45 UTC
Permalink
PUSH

Noone having similar Problems?
Post by Marc Rawer
Hi,
I'm running latest version of Agilo for trac on my site and see unexpeced
behavior on the story point burndown chart so I went online to your
demo-site and tested behavior there. I created 5 new userstories
(test{1..5}) and gave them increasing storypoints (1,2,3,5,8). I assigned
each of the user stories to a user and the srpint "story_point_test2". I
- the number of user stories was calculated correctely to total = 5
- the start of the burndown chart was marked at 19
- the ideal burndown line started at 8
=> seems like it does not take the sum for the ideal burndown but only the
last added story?
- I changed the story point of test5 to 0 and both start points drop to 0
- I changed the story points of test 4 to 20 and the start points went up
to 20
This looks like a bug to me because it only takes the last changed story
point value instead the complet sum of storypoints into account when
setting the start of the burndown chart.
Next, when a sprint is committed it seems that you can not change
responsibility anymore. Is this wanted this way?
Thanks in advance,
Marc
--
--
Follow Agilo on Twitter: http://twitter.com/agilofortrac
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-trac
http://freshmeat.net/projects/agiloforscrum

You have received this message because you are subscribed to
the "Agilo for Trac" Google Group. This group is focused on
supporting Agilo for Trac users and is moderated by
Agilo Software GmbH <http://www.agilosoftware.com>.

To post to this group, send email to agilo-/***@public.gmane.org
To unsubscribe from this group, send an email to
agilo+unsubscribe-/***@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/agilo

---
You received this message because you are subscribed to the Google Groups "Agilo for Trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilo+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Tero Isoaho
2014-03-07 11:19:38 UTC
Permalink
Hi,

I have reported similar issues.

My configuration is like this:
System Information PackageVersion Trac 1.0 Agilo 1.3.12-pro Genshi 0.7
(without speedups) mod_python 3.3.1 MySQL server: "5.5.34-MariaDB", client:
"6.0.0", thread-safe: 1 MySQLdb 1.2.4 Pygments 1.0 Python 2.5 (r25:51908,
Sep 19 2006, 09:52:17) [MSC v.1310 32 bit (Intel)] setuptools 1.4.2
Subversion 1.6.2 (r37639) jQuery1.7.2
Post by Marc Rawer
PUSH
Noone having similar Problems?
Post by Marc Rawer
Hi,
I'm running latest version of Agilo for trac on my site and see unexpeced
behavior on the story point burndown chart so I went online to your
demo-site and tested behavior there. I created 5 new userstories
(test{1..5}) and gave them increasing storypoints (1,2,3,5,8). I assigned
each of the user stories to a user and the srpint "story_point_test2". I
- the number of user stories was calculated correctely to total = 5
- the start of the burndown chart was marked at 19
- the ideal burndown line started at 8
=> seems like it does not take the sum for the ideal burndown but only
the last added story?
- I changed the story point of test5 to 0 and both start points drop to 0
- I changed the story points of test 4 to 20 and the start points went up
to 20
This looks like a bug to me because it only takes the last changed story
point value instead the complet sum of storypoints into account when
setting the start of the burndown chart.
Next, when a sprint is committed it seems that you can not change
responsibility anymore. Is this wanted this way?
Thanks in advance,
Marc
--
--
Follow Agilo on Twitter: http://twitter.com/agilofortrac
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-trac
http://freshmeat.net/projects/agiloforscrum

You have received this message because you are subscribed to
the "Agilo for Trac" Google Group. This group is focused on
supporting Agilo for Trac users and is moderated by
Agilo Software GmbH <http://www.agilosoftware.com>.

To post to this group, send email to agilo-/***@public.gmane.org
To unsubscribe from this group, send an email to
agilo+unsubscribe-/***@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/agilo

---
You received this message because you are subscribed to the Google Groups "Agilo for Trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilo+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/d/optout.
Claudio Di Cosmo
2014-03-14 14:48:33 UTC
Permalink
Hi,
Post by Tero Isoaho
I have reported similar issues.
System Information
Package Version
Trac 1.0
Agilo 1.3.12-pro
Genshi 0.7 (without speedups)
mod_python 3.3.1
MySQL server: "5.5.34-MariaDB", client: "6.0.0", thread-safe: 1
MySQLdb 1.2.4
Pygments 1.0
Python 2.5 (r25:51908, Sep 19 2006, 09:52:17) [MSC v.1310 32 bit (Intel)]
setuptools 1.4.2
Subversion 1.6.2 (r37639)
jQuery 1.7.2
we are working on a big restructure of the burndown chart feature, so that we will fix the issues that you have pointed out.

Thanks for your information!

Cheers,
Claudio Di Cosmo
Software Engineer
Agilo Software GmbH
Gruenberger Str. 54
10245 Berlin, Germany

claudio.dicosmo-CKHYNj9aYvRx67MzidHQgQC/***@public.gmane.org
http://www.agilosoftware.com

Follow us on twitter: http://twitter.com/agiloforscrum, http://twitter.com/agilofortrac

Amtsgericht Charlottenburg: HRB 127146
CEO Marion Eickmann, Andrea Tomasini
--
--
Follow Agilo on Twitter: http://twitter.com/agilofortrac
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-trac
http://freshmeat.net/projects/agiloforscrum

You have received this message because you are subscribed to
the "Agilo for Trac" Google Group. This group is focused on
supporting Agilo for Trac users and is moderated by
Agilo Software GmbH <http://www.agilosoftware.com>.

To post to this group, send email to agilo-/***@public.gmane.org
To unsubscribe from this group, send an email to
agilo+unsubscribe-/***@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/agilo

---
You received this message because you are subscribed to the Google Groups "Agilo for Trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilo+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/d/optout.
Stefano Rago
2013-07-25 08:11:44 UTC
Permalink
X-Received: by 10.180.9.232 with SMTP id d8mr54080wib.15.1374739910476;
Thu, 25 Jul 2013 01:11:50 -0700 (PDT)
X-BeenThere: agilo-/***@public.gmane.org
Received: by 10.180.206.2 with SMTP id lk2ls240482wic.40.gmail; Thu, 25 Jul
2013 01:11:48 -0700 (PDT)
X-Received: by 10.204.182.4 with SMTP id ca4mr2599316bkb.4.1374739908963;
Thu, 25 Jul 2013 01:11:48 -0700 (PDT)
Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53])
by gmr-mx.google.com with ESMTPS id nl4si2539478bkb.2.2013.07.25.01.11.48
for <agilo-/***@public.gmane.org>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 25 Jul 2013 01:11:48 -0700 (PDT)
Received-SPF: pass (google.com: domain of stefano.rago-CKHYNj9aYvRx67MzidHQgQC/***@public.gmane.org designates 209.85.214.53 as permitted sender) client-ip=209.85.214.53;
Received: by mail-bk0-f53.google.com with SMTP id e11so540240bkh.26
for <agilo-/***@public.gmane.org>; Thu, 25 Jul 2013 01:11:48 -0700 (PDT)
X-Received: by 10.205.112.142 with SMTP id es14mr5886583bkc.162.1374739908579;
Thu, 25 Jul 2013 01:11:48 -0700 (PDT)
Received: from bilbo.agile42.lan (treebeard.lan.agile42.com. [217.92.143.169])
by mx.google.com with ESMTPSA id ps10sm10576238bkb.14.2013.07.25.01.11.45
for <agilo-/***@public.gmane.org>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 25 Jul 2013 01:11:45 -0700 (PDT)
In-Reply-To: <423dbb81-a527-4a17-9830-d11e84af7414-/***@public.gmane.org>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQlQYeCrKQB3BYHyhya9UvBjursROkTphueVV8R6uVs1XZs5C4M6el+1mDLgHGJUCfAoKewd
X-Original-Sender: stefano.rago-CKHYNj9aYvRx67MzidHQgQC/***@public.gmane.org
X-Original-Authentication-Results: gmr-mx.google.com; spf=pass
(google.com: domain of stefano.rago-CKHYNj9aYvRx67MzidHQgQC/***@public.gmane.org designates
209.85.214.53 as permitted sender) smtp.mail=stefano.rago-CKHYNj9aYvRx67MzidHQgQC/***@public.gmane.org
Precedence: list
Mailing-list: list agilo-/***@public.gmane.org; contact agilo+owners-/***@public.gmane.org
List-ID: <agilo.googlegroups.com>
X-Google-Group-Id: 867806597776
List-Post: <http://groups.google.com/group/agilo/post>, <mailto:agilo-/***@public.gmane.org>
List-Help: <http://groups.google.com/support/>, <mailto:agilo+help-/***@public.gmane.org>
List-Archive: <http://groups.google.com/group/agilo>
Sender: agilo-/***@public.gmane.org
List-Subscribe: <http://groups.google.com/group/agilo/subscribe>, <mailto:agilo+subscribe-/***@public.gmane.org>
List-Unsubscribe: <http://groups.google.com/group/agilo/subscribe>, <mailto:googlegroups-manage+867806597776+unsubscribe-/***@public.gmane.org>
Archived-At: <http://permalink.gmane.org/gmane.comp.programming.scrum.agilo/2333>

Hi Mark,

thanks for the heads up, and for taking the time to describe the problem.
We will investigate this issue and come back to you as soon as we know more.
Hopefully we will come up with a fix in the next Agilo release.


Cheers

Stefano Rago
--
--
Follow Agilo on Twitter: http://twitter.com/agilofortrac
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-trac
http://freshmeat.net/projects/agiloforscrum

You have received this message because you are subscribed to
the "Agilo for Trac" Google Group. This group is focused on
supporting Agilo for Trac users and is moderated by
Agilo Software GmbH <http://www.agilosoftware.com>.

To post to this group, send email to agilo-/***@public.gmane.org
To unsubscribe from this group, send an email to
agilo+unsubscribe-/***@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/agilo

---
You received this message because you are subscribed to the Google Groups "Agilo for Trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilo+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Claudio Di Cosmo
2013-09-23 16:11:22 UTC
Permalink
Hi Marc,
We were unable to reproduce the bug. Could you please provide the steps you
use to create a user story and then assign story points? Do you use
BatchModify?
Please, can you post the trac.ini information to have a better
understanding? (you can add /about to your base trac url in order to get
it).

Regards,
Claudio
Post by Marc Rawer
Hi,
I'm running latest version of Agilo for trac on my site and see unexpeced
behavior on the story point burndown chart so I went online to your
demo-site and tested behavior there. I created 5 new userstories
(test{1..5}) and gave them increasing storypoints (1,2,3,5,8). I assigned
each of the user stories to a user and the srpint "story_point_test2". I
- the number of user stories was calculated correctely to total = 5
- the start of the burndown chart was marked at 19
- the ideal burndown line started at 8
=> seems like it does not take the sum for the ideal burndown but only the
last added story?
- I changed the story point of test5 to 0 and both start points drop to 0
- I changed the story points of test 4 to 20 and the start points went up
to 20
This looks like a bug to me because it only takes the last changed story
point value instead the complet sum of storypoints into account when
setting the start of the burndown chart.
Next, when a sprint is committed it seems that you can not change
responsibility anymore. Is this wanted this way?
Thanks in advance,
Marc
--
--
Follow Agilo on Twitter: http://twitter.com/agilofortrac
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-trac
http://freshmeat.net/projects/agiloforscrum

You have received this message because you are subscribed to
the "Agilo for Trac" Google Group. This group is focused on
supporting Agilo for Trac users and is moderated by
Agilo Software GmbH <http://www.agilosoftware.com>.

To post to this group, send email to agilo-/***@public.gmane.org
To unsubscribe from this group, send an email to
agilo+unsubscribe-/***@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/agilo

---
You received this message because you are subscribed to the Google Groups "Agilo for Trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilo+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Loading...