I found my mistake. I've added a contingent (for bug fixing) to the sprint. And the contingett was higher than the total capacity of all team members. After removing the contingent the y-axis scaling was correct.
thx. for your help mf On 8 Mrz., 16:23, Felix Schwarz <[email protected]> wrote: > Am 04.03.2010 10:26, schrieb mfreu: > > > Unfortunatelly it is not possible to access our Agilo from the > > internet. > > How does float calculate the max value ? It uses the remaining time > > of all tasks connected to the sprint ? Am I right > > Basically flot uses the max value shown. Usually this is the capacity > (if a team is connected to the sprint) or the remaining time (sum of all > tasks). > > Maybe you check the HTML source code - there should be a place with a > lot of push'es (when this was written when we did not want to depend on > simplejson). The first item is a timestamp in milliseconds, the second > an y-value. Maybe you can find out which value is so high. > > fs -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum ----- 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
