I successfuly upgraded my rt1 to rt2 and then to 3.4.5
I now want to generate some statistics and therefore had
a look at RTx-Statistics-0.1.8.tar.gz and rt3-batch-stats-0.1.tar.gz
RTx-Statistics hangs my rt3 because all tickets got the date when
the upgrade was done as closed date, therefore it is
trying to generate statistics for about 52.000 tickets for this month !!!
rt3-batch-stats-0.1 does not hang but still reports
all tickets that got migrated as closed this month.
I had a look at the metadata of one ticket for example:
Created: Fri Aug 13 16:24:18 2004
Starts: Not set
Started: Not set
Last Contact: Not set
Due: Not set
Closed: Sat Jul 08 10:52:30 2006
Updated: Tue Aug 17 14:32:53 2004 by RT_System
Tue Aug 17 14:33:07 2004 someuserid - Status changed from ‘open’ to ‘resoved’
As you can see the last timestamp in the ticket log is correct but
the “Closed:” date is set to the date the migration was done.
I now woul like to “repair” my rt3 database by doing something like in this pseudo code:
if Closed_date > Updated_date Closed_date = Updated_date
Or even better
if Closed_date > last_transaction_date Closed_date = last_transaction_date
- has sombody have had the same problems ?
- is there already a solution (script) for this problem
- has somebody an idea how to fix that directly in sql like described above ?
What are the correct table & column names for “Closed:”, “Updated:” and date of the last transaction ?
best regards, Jodok
Jodok Ole Muellers | Verizon Business
Internet Software System Engineer | Sebrathweg 20
EMEA Server & Service Management | D-44149 Dortmund, Germany
phone: +49 (0)231 972 1432 | vnet : 317 1432
mail : firstname.lastname@example.org | fax : +49 231 972 2587
pgp : gpg --keyserver blackhole.pca.dfn.de --recv-keys 5A2A106E