[rt-users] Merging two RT databases

[Tom Lahti]

> I would like to use the RT codebase instead of writing a perl script
> that interacts with the MySQL DB directly.  I think the latter approach
> would be less reliable.

If I had to do this, I would use the REST interfaces.  Do a REST request to
one RT to get ticket info, then turn around and use the REST interface on
the other to create a new ticket.

Problem is, you don't specify a ticket number when you create a new ticket.
 RT assigns one.  If you absolutely have to do that, you've no choice but to
dig into the db schema, which will be exponentially more difficult.

But you can always create a special queue just for the merged tickets, or
add a custom field and set its valued to "merged from other system" or some
such, so that you can tell them apart.

> I should also note that I can take RT offline to do the merge if necessary.

Shouldn't be necessary if you can use the REST interfaces.  Have a look at
http://wiki.bestpractical.com/view/REST.  There are convenience libraries
already written for both perl and ruby (the latter is my work).

-- 
-- ============================
   Tom Lahti
   BIT Statement LLC

   (425)251-0833 x 117
   http://www.bitstatement.net/
-- ============================