Moving Tickets in Bulk

RT Users
1

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.

Tim Gustafson
tjg@ucsc.edu
831-459-5354
Baskin Engineering, Room 313A

2

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.

–

Tim Gustafson
tjg@ucsc.edu
831-459-5354
Baskin Engineering, Room 313A

Hi Tim,

That is how I have done it to avoid the notification flurry.

Regards,
Ken

3

update Tickets set queue = 1234 where queue = 4321

That is how I have done it to avoid the notification flurry.

Thanks, I’m going to go with that for now. :slight_smile:

Tim Gustafson
tjg@ucsc.edu
831-459-5354
Baskin Engineering, Room 313A

4

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@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.