Enabling/disabling global scrips by queue?

RT Users
1

Hi folks,

I would like to disable some of the installed-by-default global Scrips and
re-enable them on a per-Queue basis.

Trolling the mailing list archives I see

which was current as of 3.8 but doesn’t look to have been updated to 4.0.

I know I can set a per-queue blank Template to disable a Scrip, but not
the other way.

What’s the current state of the art here?

  • Kevin
2

A bit more digging produced

which is tbrumm’s extension updated for 4.0.4.

Looking at 2bb0d45f898b, though, it’s overlaying the whole Scrips.pm file
rather than cleanly overlaying the relevant methods, leading me to worry
about how future-proof it is.

This really seems like it should be a core feature of RT. Would Best
Practical be interested in taking a patch if I were to work one up?

Hi folks,

I would like to disable some of the installed-by-default global Scrips and
re-enable them on a per-Queue basis.

Trolling the mailing list archives I see

GitHub - tbrumm/RT-Extension-QueueDeactivatedScrips: Deactivate global Scrips on Queue Level

which was current as of 3.8 but doesn’t look to have been updated to 4.0.

I know I can set a per-queue blank Template to disable a Scrip, but not
the other way.

What’s the current state of the art here?

  • Kevin

–
RT training in Amsterdam, March 20-21:
http://bestpractical.com/services/training.html

Help improve RT by taking our user survey:
https://www.surveymonkey.com/s/N23JW9T

3

Hey Kevin,

This really seems like it should be a core feature of RT. Would Best
Practical be interested in taking a patch if I were to work one up?

The master branch of RT, destined to become RT 4.2, already has
equivalent functionality. Scrips can be applied to queues much in the
same way that ticket CFs are applied to individual queues.

This 4.2 feature was backported for a customer as a (relatively
invasive) 4.0 extension, but the backport isn’t publicly available and I
don’t expect that to change.

If Akamai is interested in the backport before 4.2 comes out, dropping a
line to sales@bestpractical.com is the best way forward. Your other
options are waiting for 4.2.0 or living dangerously on the edge by
running git master.

Cheers,
Thomas