Sprint Burndown Chart missing old data

[Rodo]

Hello. A team of co-workers is using Agilo for Trac in their
development.

It happened to them a couple of times, that in de middle of a sprint,
without any apparent reason, Sprint Burndown Chart for the current
sprint loses old data.

I've checked table agilo_burndown_data_change (the table from which BD
chart is generated), and the data is missing in the table.

Any hint as to where the problem might be located?

In the mean time, I'm trying to find a way to regenerate table
agilo_burndown_data_change data, perhaps from agilo_burndown table.
Does anyone know if there is an easy way to do that?

Thanks.

Rodo

[Rodo]

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

[Stefano Rago]

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

[Issam]

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 <stefano.r...@agilosoftware.com>
wrote:

[Issam]

I had updated the change listener and introduced a bug there.
sorry for the false alarm