I had updated the change listener and introduced a bug there. sorry for the false alarm
On Mar 16, 10:14 pm, Issam <[email protected]> wrote: > I have similar issue with > trac 0.12 and agilo 1.3.6.2 > > I see new positive values in agilo_burndown_data_change > but no negative values and when tickets are closed I get this "[0, > {"SKIP_AGGREGATION": true}]" > > Not sure what is really going on there. > > How does that table get updated? > > Issam > > On Jan 19, 5:55 am, Stefano Rago <[email protected]> > wrote: > > > > > Hi Rodo, > > > On 18/01/12 19:50, Rodo wrote: > > > > Sorry I've missed some important information in the previous post: > > > > System Information > > > Trac: 0.11.7 > > > Python: 2.5.5 (r255:77872, Nov 23 2010, 09:50:15) [GCC 4.1.2 20071124 > > > (Red Hat 4.1.2-42)] > > > setuptools: 0.6c11 > > > SQLite: 3.7.4 > > > pysqlite: 2.6.0 > > > Genshi: 0.6 > > > Agilo: 0.9.1 > > > RPC: 1.0.6 > > > jQuery: 1.2.6 > > > This version of Agilo is quite outdated. Please consider upgrading it. > > You can find more information about the upgrade process > > here:https://agilo.agilofortrac.com/wiki/agilo/dev/users/UpgradeGuide > > > 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 Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by Agilo Software GmbH <http://www.agilosoftware.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
