[rt-users] Moving Tickets in Bulk

Landon Stewart lstewart at internap.com
Mon Sep 12 15:27:15 EDT 2016

I would personally avoid editing the database manually.  Instead I would simply stop new mail from coming in from users/staff and disable the Scrip that would send the notification until the import is done.

On Sep 12, 2016, at 9:08 AM, Tim Gustafson <tjg at ucsc.edu> wrote:
> We just finished importing around 50,000 tickets from one RT instance
> into another instance with its own large collection of tickets.  The
> rt-importer script put them into new queues (which we expected) rather
> than the ones we had already created in the destination system for the
> cut-over.  I went in to start moving tickets from the imported queues
> into the correct ones, and noticed that it's kinda slow, and it's
> sending notification e-mails (via scrips) for each move.
> What's the safest way to move tickets from one queue to another in
> bulk without sending notification e-mails?  Is it safe to just do:
> update Tickets set queue = 1234 where queue = 4321
> in Postgres?  I don't care so much if the ticket's transaction history
> doesn't show the move.

More information about the rt-users mailing list