We’re running RT 4.0.5. If I go to Configuration->Global->Scrips->Select,
I don’t see any scrips. So where are the global scrips (e.g., email
comments to AdminCc’s) hiding? They’re in initialdata, but editing them
there won’t help, will it?
I’m asking because sometimes we want to archive the fact that we did a
certain task for a ticket, but it doesn’t need to fill everyone’s mailbox.
I’d like to set up a Scrip where, if I input some (highly unique) string
in the Subject line, then RT doesn’t email all AdminCc’s. (Even cooler
would be if the unique string gets removed or modified before hitting the
database, so that if someone comments on that comment for some reason, the
email will go to AdminCc’s.) Preferably, this would be on a queue by
queue basis, though if we make the string random enough, maybe it could be
global and nobody would notice.
A quick search of the archives & wiki didn’t turn anything up.
Thanks,
-Amir Karger
We’re running RT 4.0.5. If I go to Configuration->Global->Scrips->Select,
I don’t see any scrips. So where are the global scrips (e.g., email
comments to AdminCc’s) hiding? They’re in initialdata, but editing them
there won’t help, will it?
I’m asking because sometimes we want to archive the fact that we did a
certain task for a ticket, but it doesn’t need to fill everyone’s mailbox.
I’d like to set up a Scrip where, if I input some (highly unique) string
in the Subject line, then RT doesn’t email all AdminCc’s. (Even cooler
would be if the unique string gets removed or modified before hitting the
database, so that if someone comments on that comment for some reason, the
email will go to AdminCc’s.) Preferably, this would be on a queue by
queue basis, though if we make the string random enough, maybe it could be
global and nobody would notice.
Why not just use the normal notification squelching available on the
ticket reply page?
See the “Scrips and Recipients” below the message box on the reply page.
Where are the global scrips (e.g., email comments to AdminCc’s) hiding?
I’d like to set up a Scrip where, if I input some (highly unique) string
in the Subject line, then RT doesn’t email all AdminCc’s. (Even cooler
would be if the unique string gets removed or modified before hitting
the
database, so that if someone comments on that comment for some reason,
the
email will go to AdminCc’s.) Preferably, this would be on a queue by
queue basis, though if we make the string random enough, maybe it could
be
global and nobody would notice.
Why not just use the normal notification squelching available on the
ticket reply page?
See the “Scrips and Recipients” below the message box on the reply page.
Ah, I didn’t give enough detail. We have a bash script that runs a command
and emails RT with the results. This lets us record what we actually did
(and the stdout result) into the ticket without cutting and pasting from
our ssh window. But it’s not going through the web interface.
(It’s your fault for giving us diverse UIs!)
-Amir
Ah, I didn’t give enough detail. We have a bash script that runs a command
and emails RT with the results. This lets us record what we actually did
(and the stdout result) into the ticket without cutting and pasting from
our ssh window. But it’s not going through the web interface.
(It’s your fault for giving us diverse UIs!)
We expose squelching via email headers.
If you don’t want RT to notify at all about the email your command
sends, add the following header:
X-RT-Squelch: yes
If you want to squelch a certain set of recipients RT might otherwise
mail, include a header like:
RT-Squelch-Replies-To: foo@example.com,bar@example.com