On Thu, Jan 15, 2004 at 09:18:29PM +0100, Robert Kehl wrote:

...

Can't you just update the queue_id in the ticket to table to reflect the new queue ?

You can, for sure, but it's not recommended to touch the raw database when there'se no need to.

Yepp. And the GenericAgent will also add the move action to the ticket history. :)

Robert Kehl

Martin Edenhofer -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!

On Thursday, January 15, 2004 9:47 PM Mark Mertel wrote:

ok - its just the database guy deep inside trying to get out. help, i'm trapped in a SQL puzzle !

Put on your blue jeans, now you're the script guy: # cd /opt/otrs # cp Kernel/Config/GenericAgent.pm.dist Kernel/Config/Mover.pm # vi Mover.pm Add the following as the only job where it reads "# insert your jobs (see Kernel/Config/GenericAgent.pm.examples)": # -- # [name of job] -> move all tickets from Raw to NewQueue # -- 'move tickets from Raw to NewQueue' => { # get all tickets with these properties Queue => 'Raw', States => ['new', 'open'], Locks => ['unlock'], # new ticket properties New => { Queue => 'NewQueue', Note => { From => 'GenericAgent', Subject => 'Moved!', Body => 'Moved from "Raw" to "NewQueue" - cleanup done.', ArticleType => 'note-internal', # note-internal|note-external|note-report }, }, }, Now let it run: # bin/GenericAgent.pl -c 'Kernel::Config::Mover' hth, Robert Kehl -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Tel. +49 (0)6172 4832388