Custom condition help

I have a custom condition setup in the web interface under global-scrips
with the following in the custom condition box:

$self->TicketObj->status eq ‘open’

Based on the example in RT Essentials pg 78 this should fire whenever
the ticket status changes to open.

Then for action I have the drop down notify requestors set and a notify
owner template set. In the condition dropdown I have user defined
selected. I’m not the requestor either so NotifyActor doesn’t play in
here.

Any ideas why an email isn’t being sent to the requestor? I’m looking
at the ticket history to verify that it’s no working.

Thanks,
-Tim

Just thought to look in the logs and this is what is recorded:

IsApplicable failed: RT::ticket::status Unimplemented in
RT::Condition::UserDefined.

Does this mean the book example is bogus?-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Flynn,
Timothy J
Sent: Friday, April 07, 2006 9:38 AM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Custom condition help

I have a custom condition setup in the web interface under global-scrips
with the following in the custom condition box:

$self->TicketObj->status eq ‘open’

Based on the example in RT Essentials pg 78 this should fire whenever
the ticket status changes to open.

Then for action I have the drop down notify requestors set and a notify
owner template set. In the condition dropdown I have user defined
selected. I’m not the requestor either so NotifyActor doesn’t play in
here.

Any ideas why an email isn’t being sent to the requestor? I’m looking
at the ticket history to verify that it’s no working.

Thanks,
-Tim
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

We’re hiring! Come hack Perl for Best Practical:

Just thought to look in the logs and this is what is recorded:

IsApplicable failed: RT::ticket::status Unimplemented in
RT::Condition::UserDefined.

Does this mean the book example is bogus?

It means you’ve typed “status” when you meant to type “Status”

Thanks Jesse,

It is lowercase in the book. I’ll try that… It works!

-Tim-----Original Message-----
From: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Friday, April 07, 2006 9:44 AM
To: Flynn, Timothy J
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Custom condition help

On Fri, Apr 07, 2006 at 09:42:43AM -0500, Flynn, Timothy J wrote:

Just thought to look in the logs and this is what is recorded:

IsApplicable failed: RT::ticket::status Unimplemented in
RT::Condition::UserDefined.

Does this mean the book example is bogus?

It means you’ve typed “status” when you meant to type “Status”