On Dec 18, 2008, at 9:01 PM, Brian Friday wrote:
Thanks Drew,
Your tips led me to the library issues. RT2 can not be exported
without the same perl modules used for RT2. Once I installed the
correct libraries everything exported correctly.
My import however still has one snag, or rather
On Dec 31, 2008, at 10:45 AM, Kevin Falcone wrote:
On Dec 18, 2008, at 9:01 PM, Brian Friday wrote:
Thanks Drew,
Your tips led me to the library issues. RT2 can not be exported
without the same perl modules used for RT2. Once I installed the
correct libraries everything exported
On Dec 31, 2008, at 4:11 PM, Brian Friday wrote:
On Dec 31, 2008, at 10:45 AM, Kevin Falcone wrote:
On Dec 18, 2008, at 9:01 PM, Brian Friday wrote:
Thanks Drew,
Your tips led me to the library issues. RT2 can not be exported
without the same perl modules used for RT2. Once I installed
On Dec 31, 2008, at 1:31 PM, Kevin Falcone wrote:
Actually I did, latest, though I guess I could be more clear and
said SVN version as well.
I don't trust 'latest' as a version number since people occasionally
download the
incredibly old version on downloads.bestpractical.com rather than
On Dec 31, 2008, at 5:14 PM, Brian Friday wrote:
The status exists in the dumped tickets but that status is not
maintained in the dumpfile to rt3
push rather all resolved tickets are pushed back to new a status we
did not have in RT2.
The only change made to Status during the dumpfile -
On Dec 31, 2008, at 6:28 PM, Brian Friday wrote:
On Dec 31, 2008, at 2:58 PM, Kevin Falcone wrote:
I assume select Status from Tickets where id = t-58818; returns
resolved?
Correct
Ok, so it isn't a mapping issue from old custom status to new custom
status which is what I was worried
Thanks Drew,
Your tips led me to the library issues. RT2 can not be exported
without the same perl modules used for RT2. Once I installed the
correct libraries everything exported correctly.
My import however still has one snag, or rather 51,000 or so snags. I
have 51,000 tickets with the
When I upgraded several years ago, I had to run rt2-to-dumpfile BEFORE I
installed RT3 at all. Something about the version of SearchBuilder (I
think) that RT# used broke the data export of RT2. At one point I was
very good with the procedure for that upgrade, but my memory seems to
have been
Hello all,
I am using the RT2-to-RT3 migration tool (latest) to migrate a RT2
instance (Mysql 3.23, DB is 1+ GB in size) from 2.0.14 to RT 3.6.7
(Mysql 5). I have copied the original RT2 install, and the new RT3
from their respective machines to a go between system. I've fixed the
paths
