On 20 May, 2009, at 8:31 , Vignesh Ganesan wrote:
> Hello Andreas, Hi, and please use the agilo user group :-) > Has this bug been fixed yet? I've recently started using Agilo in our > development and find that the date still seems a bit off. Here's the > chart: If there's ever been a bug than you can now check the status online at https://dev.agile42.com ;-) > http://dl.getdropbox.com/u/455986/burndown_dateoffset.png > > I took this screenshot on Wenesday 20th May 0630 GMT/UTC. I don't > suppose there are many places right now, with already at 21st May, > that too with the day completed. Or aM I just reading this chart > wrong? Please let me know, Well it seems that you server has a different timezone... as of now the charts are relative to the server timezone, and in 0.8 this has been fixed and everytime/date is now saved as UTC timestamp and converted on the clientside to the actual timezone :-) > Thanks, YAW > Best, Best > Vignesh. ANdreaT > > On Jan 6, 12:09 am, Andrea Tomasini <[email protected]> > wrote: >> On 5 Jan, 2009, at 16:14 , Robby wrote: >> >>> Hi guys, >> >> Hi Robby :-) >> >>> Running agilo 0.7.2.5-r1150-20081220. I have my backlog entered in, >>> however theburndownchart dates appear to be incorrect. See >>> http://public.robbyd.fastmail.fm/agilo-charts.png >> >>> The chart shows today as being the 7th (not the 5th). And yes, the >>> dateon the box is correct. That above image was produced on the box >>> that showed "Mon Jan 5 15:04:38 UTC 2009" as the return from adate >>> command (synched with NTP, and verified to coorespond with other >>> boxes >>> in our environment). The box IS running in VMWare, although I'm not >>> sure how that would affect things if the systemdateitself is >>> correct. I haven't changed or corrected thedatevery recently at all >>> AFAIK... Is there something I can do to force the chart to be >>> regenerated? This is probably not a bug...just that something cached >>> needs to be cleared out...but I just want to make sure, and to see >>> how >>> to fix thisproblemon our installation. >> >> I think there are 2 problems... one is that the last dot is drown >> (due >> to actual limitation of matplotlibdatechart) at the midnight of the >> next day. There was a bug about the position of the today "green" >> bar, >> and has been fixed too... as far as I can tell. We are anyway working >> hard to remove the dependencies with matplotlib and numpy, adopting a >> javascript based chart library ;-) so we will have to port all the >> charts again, Felix is already working on it... >> >> In order to have hot fixes you need to be a "supported" customer, so >> you will have to wait till the next "official" release which will be >> on the 19.01.2008 :-) >> >>> Thanks! >> >> YAW >> >>> Robby >> >> 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 -~----------~----~----~----~------~----~------~--~---
