David,
I could be wrong, but I think it is a matter of timing. My experience with
trying to stop a transaction in RT is that you're always a little late in
the process. Once RT has recorded that a ticket *has* changed Queues, I
believe it is already too late. You can change it back, but you can't
I had to re-type part of the code to post it to the mailing list and
the $Transaction / $transaction came from there, it is actually fine in
the custom condition:
my $Transaction = $self->TransactionObj;
return($Transaction->Type eq "Set" && $Transaction->Field eq "Queue" &&
$Transaction->Ol
David,
Maybe it's just the way the typing looks, but it looks like you defined my
$Transaction with a capitol "T", but when you specify it in the code, it has
a lowercase "t". This might cause a problem. What did you see in your log
file?
Kenn
LBNL
On Mon, Sep 20, 2010 at 12:53 PM, David Moreau
This is so weird.. would it be a bug ? Because the code certainly
doesn't behave the way I would expect.
I've tried several things as a global scrip as Kenneth recommended:
Condition: User Defined
Action: User Defined
Template: Blank
Custom Condition:
my $Transaction = $self->TransactionObj;
You need to have a global scrip that check for a queue change
and if the previous queue was the queue that you want to track
or react to exits.
Cheers,
Ken
On Mon, Sep 20, 2010 at 01:19:32PM -0400, David Moreau Simard wrote:
> Hi,
>
> We're running RT 3.8.8 and we need to fire a scrip when a tic
Hi,
We're running RT 3.8.8 and we need to fire a scrip when a ticket is
transferred away from a queue (to any possible destination).
The condition built into RT "On queue change" only seems to fire when a
ticket is transferred in but not when a ticket is transferred out.
I've tried various