I’ve got an RT 1.0.7 install with thousands of tickets, and I’d like to
upgrade to RT 3.0.5. There’s an script to upgrade from RT 2.X to 3.X, (
http://www.fsck.com/pub/rt/devel/rt2-to-rt3.tar.gz )
but I don’t see one for upgrading from 1.X to 3.X, or even from 1.X to
2.X.
Does anyone know of a relatively painless way to upgrade from 1.0.7 to
3.0.5? Thanks.
Doug Wilson
Project Director - Information Systems
Virtual Technology Corporation
703-658-7050
dwilson@virtc.com
Doug Wilson wrote:
but I don’t see one for upgrading from 1.X to 3.X, or even from 1.X to
2.X.
http://www.fsck.com/pub/rt/contrib/2.0/rt-addons/import-1.0-to-2.0
good luck!
Phil Homewood, Systems Janitor, http://www.SnapGear.com
pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances
I run RT2.0.15 and am performing some searches. I was
interested in all tickets in a particular queue
created in July. I have nothing set for ‘status’, so
I would expect all tickets (even dead) to show up.
The dead tickets do not show up. In fact, if I
specifically search for ‘dead’ tickets, I get no
results. I can manually go to the ‘dead’ ticket, and
it’s still accessible.
Is this a bug in RT2?
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
Joseph Spenner wrote:
I would expect all tickets (even dead) to show up.
The dead tickets do not show up. In fact, if I
specifically search for ‘dead’ tickets, I get no
results. I can manually go to the ‘dead’ ticket, and
it’s still accessible.
Is this a bug in RT2?
No, it’s a feature. Dead tickets are, well, dead. They’re
effectively deleted. They’re not supposed to be able to
be searched.
Phil Homewood, Systems Janitor, http://www.SnapGear.com
pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances
Joseph Spenner wrote:
I would expect all tickets (even dead) to show up.
The dead tickets do not show up. In fact, if I
specifically search for ‘dead’ tickets, I get no
results. I can manually go to the ‘dead’ ticket,
and
it’s still accessible.
Is this a bug in RT2?No, it’s a feature. Dead tickets are, well, dead.
They’re
effectively deleted. They’re not supposed to be able
to
be searched.
So, the selection of “dead” in the ‘status’ dropdown
will never yield any useful results?
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
Joseph Spenner wrote:
So, the selection of “dead” in the ‘status’ dropdown
will never yield any useful results?
Correct. Perhaps its inclusion there could be considered
a bug in itself.
Phil Homewood, Systems Janitor, http://www.SnapGear.com
pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances
Doug Wilson wrote:
but I don’t see one for upgrading from 1.X to 3.X, or even from 1.X to
2.X.http://www.fsck.com/pub/rt/contrib/2.0/rt-addons/import-1.0-to-2.0
I’ve done the 1.X → 3.X upgrade a number of times without any trouble, but
there are a couple of pitfalls it might be worth noting. It can be quite time
consuming: importing from 1.0 to 2.0 is relatively quick, as the 1.0
database structure is relatively minimal. 2.0 → 3.0 is much slower. Doing a
trial run on a spare machine is probably a good move so you can estimate how
much downtime you might face.
Another thing to note is that you never actually have to run the rt2
instance - it’s only there for data transfer. I’d recommend not bothering to
set Apache up for it: if you use mod_perl you can’t run an rt2 and rt3
instance on the same Apache instance (you need at least 2 sets of processes
and 2 config files).
cheers
john