Hi Rohit, (hope thats the right name)
> Thaks for the help. > > After updating Agilo, the capacity issue in team statistics page has > been resolved. But the sprint burndown chart issue still persists. Good to hear that! > Earlier this problem was not there. It started from the day i wrote a > script to access the trac.db databse in order to fetch some information. > I ran the script on live database, when tracd server was on. After that > the burndown chart started behaving improperly. > > From what i have observed, when i change remaining time of any task, the > chart does not update simultaneously. I see the accumulated change after > a day. Earlier the updation on chart was simultaneous. This is bad, if the changes only ever show up on the next day, instead of after a page reload then something is wrong. You could make a copy of your environment (don't forget the database if it's not sqlite) available to me, then I could take a look at that and maybe figure out what is causing this. (You can leave out attachements if you use them to keep the filesize down). Perhaps you could also give me access to the sql script you ran against the database, perhaps I can get a hint from that why this is happening now. Regards, Martin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
