Exporting tickets from one RT to another

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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?

Thanks.

Mike

Mike Friedman IST/System and Network Security
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
http://socrates.berkeley.edu/~mikef http://security.berkeley.edu

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBRbDza60bf1iNr4mCEQJFQgCdG/3fPFIRoCqsh+C8v7TbidoX3SEAn0Fn
9qiVKyCHO6WIKZtEDJorDe41
=CFQM
-----END PGP SIGNATURE-----

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.

James Moseley

         Mike Friedman                                                 
         <mikef@ack.berkel                                             
         ey.edu>                                                    To 
         Sent by:                  rt-users@lists.bestpractical.com    
         rt-users-bounces@                                          cc 
         lists.bestpractic                                             
         al.com                                                Subject 
                                   [rt-users] Exporting tickets from   
                                   one RT to another                   
         01/19/2007 10:35                                              
         AM                                                            

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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?

Thanks.

Mike

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

iQA/AwUBRbDza60bf1iNr4mCEQJFQgCdG/3fPFIRoCqsh+C8v7TbidoX3SEAn0Fn
9qiVKyCHO6WIKZtEDJorDe41
=CFQM
-----END PGP SIGNATURE-----
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

jmoseley@pgtv.com writes:

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.

I’d say you would probably have to do a lot more than that to
make all references to users, queues, transactions, and so on, valid.

My 10000th ticket sits in queue 14 and was last updated by user 98.

Leif Nixon - Systems expert
National Supercomputer Centre - Linkoping University