At the moment, we have a set of global scrips that apply to all queues. We
want to migrate to using per-queue scrips since many of the queues have
different needs. Is there an easy way to take the existing global scrips and
apply them to all queues (and then delete the global scrips)?
Amy,
I brought this up with Jesse, and he thought that you could simply
update the scrips table in the DB with the new information. Check
the archives for more detail. That is how we are going to approach
this process here.
KenOn Tue, Sep 16, 2008 at 12:25:28PM -0400, amy.rich@tufts.edu wrote:
At the moment, we have a set of global scrips that apply to all queues. We
want to migrate to using per-queue scrips since many of the queues have
different needs. Is there an easy way to take the existing global scrips and
apply them to all queues (and then delete the global scrips)?
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
At the moment, we have a set of global scrips that apply to all queues. We
want to migrate to using per-queue scrips since many of the queues have
different needs. Is there an easy way to take the existing global scrips and
apply them to all queues (and then delete the global scrips)?
here is a script I used a while ago to do this, you should adjust path
at top on the script and also add unwanted queues in @queues_blacklist
if needed.
should works fine but … test it on test RT instance before your
production RT maybe 
global2perqueue-scrips.pl (2.03 KB)