Updating from 2.0.15 to 3.0.11

Is there any sane way to get the tickets from the 2.0.15 instance into
the 3.0.11 database?

Scott

Scott Dexter

Is there any sane way to get the tickets from the 2.0.15 instance into
the 3.0.11 database

Define “sane”. So far there exists exactly one automated way to do it,
but you don’t say whether you know of it, nor whether you think that
way is sane.

http://download.bestpractical.com/pub/rt/devel/
rt2-to-rt3 package

Scott Dexter wrote:

Ruslan U. Zakirov wrote:

http://download.bestpractical.com/pub/rt/devel/
rt2-to-rt3 package

Scott Dexter wrote:

Is there any sane way to get the tickets from the 2.0.15 instance
into the 3.0.11 database?

Scott

I’ve tried this script…it fails horribly just about every time I use
it. :frowning:

Scott Dexter
Jr Unix Administrator
Ingenta, Inc.
111R Chestnut Street, Providence, RI 02903
T +1.401.331.2014
F +1.401.331.2015
E scott.dexter@ingenta.com
AIM scottder517

Scott Dexter wrote:

Ruslan U. Zakirov wrote:

http://download.bestpractical.com/pub/rt/devel/
rt2-to-rt3 package

Scott Dexter wrote:

Is there any sane way to get the tickets from the 2.0.15 instance
into the 3.0.11 database?

Scott

I’ve tried this script…it fails horribly just about every time I use
it. :frowning:

It’s only known sane way. You can try fix it or hire perl guru.
RT2 instance may have some artefacts that are not well handled.
You can try 3.0.4-6 instead of 3.0.11 cause this script was mainly
writen/fixed at that period of time.

	Best regards. Ruslan.