RT1 to RT2 to RT3 upgrade

Hi,

I’ve just started upgrading our current RT1.0.7 to RT2.0.15 on the way to
RT3.2.1 and I have a couple of problems with the import-1.0-to-2.0 script.

Is the import-1.0-to-2.0 from
http://download.bestpractical.com/pub//rt/contrib/2.0/rt-addons/ still the
current one?

If so then has anyone else had problems migrating tickets with Areas defined
across from RT1 to RT2? The area info seems to get disabled in the tickets
when I run it.

And the history on all the imported RT1 tickets shows the time of any
transactions/changes as the time of the import - losing a lot of useful info
in the process.

Am I missing a conversion step somewhere?

Is this expected behaviour?

Is there an alternative method that retains all the info?

Thanks in advance.

cheers,

Ian Gilmour

CONFIDENTIALITY AND DISCLAIMER NOTICE

This message and any attachment is confidential and is protected by
copyright. If you are not the intended recipient, please email the sender or
telephone +44 (0)1442 213440 and delete this message and any attachment from
your system. Dissemination and or copying of this email is prohibited if you
are not the intended recipient.

We believe, but do not warrant, that this email and any attachments are
virus free. You should take full responsibility for virus checking.

No responsibility is accepted by FUJIFILM Electronic Imaging Limited for
personal emails or emails unconnected with FUJIFILM Electronic Imaging
Limited’s business.

OK. I massaged the import script so the Areas are now tranferred across
ok (I had to change a “Parent => 0” to “Parent =>1” statement on one of
the queue keyword Create statements to do it though?).

But I’m still scratching my head over the timestamp problem. Dumping the
ISO date/time just prior to the $ticket->Import call, in the
import-1.0-to-2.0 script, the date/time looks fine. But in the database
all imported tickets and transactions have the time of the import in any
datetime fields transferred across. Tickets created via the RT2 Web
interface look fine.

Any clues?

I’m sure I’m doing something stupid but I can’t see it?

perl 5.8.5
mysql 4.0.21
apache 2.0.51, with fastcgi

cheers,

Ian

PS Apologies for the disclaimer at the end - I have no control over it.-----Original Message-----
From: Ian Gilmour [mailto:ian.gilmour@ffei.co.uk]
Sent: 04 October 2004 08:57
To: Rt-Users (E-mail)
Subject: [rt-users] RT1 to RT2 to RT3 upgrade

Hi,

I’ve just started upgrading our current RT1.0.7 to RT2.0.15 on the way to
RT3.2.1 and I have a couple of problems with the import-1.0-to-2.0 script.

Is the import-1.0-to-2.0 from
http://download.bestpractical.com/pub//rt/contrib/2.0/rt-addons/ still the
current one?

If so then has anyone else had problems migrating tickets with Areas defined
across from RT1 to RT2? The area info seems to get disabled in the tickets
when I run it.

And the history on all the imported RT1 tickets shows the time of any
transactions/changes as the time of the import - losing a lot of useful info
in the process.

Am I missing a conversion step somewhere?

Is this expected behaviour?

Is there an alternative method that retains all the info?

Thanks in advance.

cheers,

Ian Gilmour

CONFIDENTIALITY AND DISCLAIMER NOTICE

This message and any attachment is confidential and is protected by
copyright. If you are not the intended recipient, please email the sender or
telephone +44 (0)1442 213440 and delete this message and any attachment from
your system. Dissemination and or copying of this email is prohibited if you
are not the intended recipient.

We believe, but do not warrant, that this email and any attachments are
virus free. You should take full responsibility for virus checking.

No responsibility is accepted by FUJIFILM Electronic Imaging Limited for
personal emails or emails unconnected with FUJIFILM Electronic Imaging
Limited’s business.