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 wrote:
>
> We just finished importing around
>> 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. :)
--
Tim Gustafson
t...@ucsc.edu
831-459-5354
Baskin Engineering, Room 313A
-
RT 4.4 and RTIR training sessions, and a new w
On Mon, Sep 12, 2016 at 09:08:44AM -0700, Tim Gustafson 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 h
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
