> Let me just say that no mention of $NotifyActor is made in the book
> until the Appendix - maybe it should get some more importance as I
> would have expected the default behaviour to be the opposite one.
Updates to the wiki or documentation patches to make it clearer are
certainly welcome.
> (
On 02/12/10 14:17, Kevin Falcone wrote:
This makes all the difference in the world.
What is your value for $NotifyActor in your config (and you should
read the docs associated with it)
-kevin
Uhm ok - I'll take in the critic, now that you point it it was pretty
obvious :-)
Let me ju
On Thu, Dec 02, 2010 at 09:48:02AM +, Giuseppe Sollazzo wrote:
> Hi Kevin and Kenneth
> sorry for the trim. I'll paste it again below.
>
> The requestor and creator of the tickets (if that's what you mean by
> "using reply") are the same person (i.e. I create a ticket with my
> RT account - us
Hi Kevin and Kenneth
sorry for the trim. I'll paste it again below.
The requestor and creator of the tickets (if that's what you mean by
"using reply") are the same person (i.e. I create a ticket with my RT
account - using LDAP), and set my e-mail address (using LDAP
autocompletion) as request
Giuseppe,
I was just gonna ask you the same Question Kevin did.
Kenn
On Wed, Dec 1, 2010 at 9:15 AM, Kevin Falcone wrote:
> On Mon, Nov 29, 2010 at 04:00:15PM +, Giuseppe Sollazzo wrote:
> >I'm playing with our rather vanilla installation of RT in which we're
> supposed to have, at
> >
On Mon, Nov 29, 2010 at 04:00:15PM +, Giuseppe Sollazzo wrote:
>I'm playing with our rather vanilla installation of RT in which we're
> supposed to have, at
>least for the moment, one general queue from which tickets will be moved
> into two other real
>queue according to the depa
Just to add a little bit of info, the "Admin Correspondence" template
only did
"RT-Attach-Message: yes
Config->Get('WebURL')}Ticket/Display.html?id={$Ticket->id} >
{$Transaction->Content()}"
so I was not sure it e-mailed (it should). To be sure, I created a
template called "Reply" attached
Hi Kenneth,
thanks a lot for your help. These are the 4 scrips that use the "On
Correspond" condition"
"On Correspond Notify AdminCcs" TransactionCreate On
Correspond Notify AdminCcs Admin Correspondence
"On Correspond Notify Other Recipients" TransactionC
Giuseppe,
List for me the following information for each Notification scrip that uses
"On Correspond" as the condition:
Description:
Condition:
Action:
Template:
Stage:
Unless you have specific information in a template from Ticket/Custom Field
data being set by a scrip running in "TransactionBa
Hi Kenneth,
it's actually the requestor.
But if I set up a Cc (a one-time Cc) the same thing happens.
Giuseppe
On 30/11/10 17:00, Kenneth Crocker wrote:
Giuseppe,
Exactly who is NOT getting a notification on Correspondence? Compare
their role with the recipients. If they are not listed as a
Giuseppe,
Exactly who is NOT getting a notification on Correspondence? Compare their
role with the recipients. If they are not listed as a "Cc" Watcher (for
example) on either the Queue or the Ticket, then they will not get a
notification as a "Cc", etc.
Kenn
LBNL
On Tue, Nov 30, 2010 at 8:04 AM
On 29/11/10 17:48, Kenneth Crocker wrote:
Giuseppe,
Most likely, you do not have a notification scrip for "On Correspond".
I believe the book has several good examples on how to build a simple
scrip like that. Anyway, check your Global/Queue notification scrip
sand see if that's the case. Hop
Giuseppe,
Most likely, you do not have a notification scrip for "On Correspond". I
believe the book has several good examples on how to build a simple scrip
like that. Anyway, check your Global/Queue notification scrip sand see if
that's the case. Hope this helps.
Kenn
LBNL
On Mon, Nov 29, 2010
Hi everyone,
I'm playing with our rather vanilla installation of RT in which we're
supposed to have, at least for the moment, one general queue from which
tickets will be moved into two other real queue according to the department.
Trying to configure mail in and mail out, I happen to have a
14 matches
Mail list logo
