[rt-users] Notify owners of new ticket not working

[Cena, Stephen (ext. 300)]

Ah; then it looks like it's a bug in the plug-in itself. It is in fact
notifying the potential owners of a ticket, whether an Owner is
specified or not. This isn't bad. I could just create a custom Template
that would rework the email to let everyone know who has the ticket.

Does anyone have a custom Scrip they use when a ticket is created, and
no owner is specified that all potential owners get notified? I also
need to look at the Perl modules someone recommended earlier, but I
thought this plug-in might do the trick.


Message: 14
Date: Wed, 19 Jun 2013 16:28:30 +0200
From: Kai Storbeck <kai at xs4all.nl>
To: <rt-users at lists.bestpractical.com>
Subject: Re: [rt-users] Notify owners of new ticket not working
	totally
Message-ID: <14ae2cf3eabb98a1577c145a18215373 at xs4all.nl>
Content-Type: text/plain; charset=UTF-8; format=flowed

On 2013-06-19 15:49, Cena, Stephen (ext. 300) wrote:
> I'm using the NotifyOwner plug in for extra notifications:
>
http://search.cpan.org/dist/RT-Extension-NotifyOwners/lib/RT/Extension/N
otifyOwners.pm
> [1]
> 
> The Scrip is working, however its also sending out an email even if
> the ticket gets an owner. It should only fire when the ticket is
> created and the owner is "Nobody In Particular".
> 
> Here is my Scrip:
> ============================
> Desc: On Create Unowned Ticket
> Condition: On Create
> Action: Notify Potential Owners
> Template: Global Template: Potential owners notification
> Stage: TransactionCreate
> 
> Custom Condition:
> return 1 if $self->OwnerObj->Id == $RT::Nobody->Id;
> return 0;
> =============================
> 
> Is my custom condition wrong?

Hi Stephen,

You should select "Userdefined" from the Condition pulldown menu, or it 
will not run your custom condition code block.

Regards,
Kai


------------------------------

--------
rt-users mailing list
rt-users at lists.bestpractical.com
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users



End of rt-users Digest, Vol 111, Issue 20
*****************************************