I’d suggest searching the list archives as others have probably had similar
questions. With that said, you would need to upgrade the schema on the 2nd
database as well. Then do a database dump on the appropriate tables.
Since you’ll probably have duplicate ticket numbers, you would need to
create new ticket numbers in the dumped database tables as well as remove
the tickets you no longer want.
Then simply restore those modified tables into the new database.
If you used different $rtnames across installations, you’ll want to update
that string in the tickets as well so they all match.
Sent by: firstname.lastname@example.org
[rt-users] Exporting tickets from
one RT to another
-----BEGIN PGP SIGNED MESSAGE-----
Is there an easy way to export a set of tickets (say, all tickets in one
or more specific queues) so they can be inserted into another RT instance?
Here’s the situation:
I’ll be setting up a new RT instance that will start out using a database
that currently is running on another (older) RT 3.x.x system. This means,
presumably, just moving that database over (and upgrading it because of
schema changes in the newer version of RT).
Meanwhile, I have another existing RT, at version 3.4.5, from which I’ll
eventually want to move some or all tickets into that new RT.
Any suggestions on the best (if any) way to do this?
Mike Friedman IST/System and Network Security
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
Socrates and Berkeley Scholars Web Hosting Services Have Been Retired | Web Platform Services http://security.berkeley.edu
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
-----END PGP SIGNATURE-----
Community help: http://wiki.bestpractical.com
Commercial support: email@example.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com