Notify owner issues, 2.1.83

I’m still having issues on this notify owner scrip. If an owner updates a
ticket, the scrip does not trigger. If a non-owner updates the ticket, the
owner gets an update.

Looking into this more, if any watcher updates the ticket, that watcher
(owner, admin) doesn’t get the update, regardless of the scrip action.

Is this the “new way” for rt3? Or a bug?

matthew zeier | “Nothing in life is to be feared.
InteleNet Communications, Inc. | It is only to be understood.”
(949) 784-7904 | - Marie Curie

This is how RT2 and RT3 have always been. It is not a change.
If your RT2 does something different, a local user has altered RT’s
code.On Fri, Mar 07, 2003 at 03:24:57PM -0800, matthew zeier wrote:

I’m still having issues on this notify owner scrip. If an owner updates a
ticket, the scrip does not trigger. If a non-owner updates the ticket, the
owner gets an update.

Looking into this more, if any watcher updates the ticket, that watcher
(owner, admin) doesn’t get the update, regardless of the scrip action.

Is this the “new way” for rt3? Or a bug?


matthew zeier | “Nothing in life is to be feared.
InteleNet Communications, Inc. | It is only to be understood.”
(949) 784-7904 | - Marie Curie


rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

http://www.bestpractical.com/rt – Trouble Ticketing. Free.

Seriously? I’ve done two seperate RT2 installs and both behave the same.

OnTransaction NotifyOwner with template Transaction

I diff’d Notify.pm from a fresh download of rt2.0.15 and what I have
installed and it came out the same. Did the same for AnyTransaction.pm,
same thing.

Where would some local user (me) have altered RT?

This is how RT2 and RT3 have always been. It is not a change.
If your RT2 does something different, a local user has altered RT’s
code.

I’m still having issues on this notify owner scrip. If an owner updates
a

ticket, the scrip does not trigger. If a non-owner updates the ticket,
the

owner gets an update.

Looking into this more, if any watcher updates the ticket, that watcher
(owner, admin) doesn’t get the update, regardless of the scrip action.

Is this the “new way” for rt3? Or a bug?


matthew zeier | “Nothing in life is to be feared.
InteleNet Communications, Inc. | It is only to be understood.”
(949) 784-7904 | - Marie Curie


rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel


http://www.bestpractical.com/rt – Trouble Ticketing. Free.

http://www.fsck.com/rtfm/article.html?id=5#73On Fri, Mar 07, 2003 at 03:35:37PM -0800, matthew zeier wrote:

Seriously? I’ve done two seperate RT2 installs and both behave the same.

OnTransaction NotifyOwner with template Transaction

I diff’d Notify.pm from a fresh download of rt2.0.15 and what I have
installed and it came out the same. Did the same for AnyTransaction.pm,
same thing.

Where would some local user (me) have altered RT?

  • mz

----- Original Message -----
From: “Jesse Vincent” jesse@bestpractical.com
To: “matthew zeier” mrz@intelenet.net
Cc: rt-devel@lists.fsck.com
Sent: Friday, March 07, 2003 3:26 PM
Subject: Re: [rt-devel] notify owner issues, 2.1.83

This is how RT2 and RT3 have always been. It is not a change.
If your RT2 does something different, a local user has altered RT’s
code.

On Fri, Mar 07, 2003 at 03:24:57PM -0800, matthew zeier wrote:

I’m still having issues on this notify owner scrip. If an owner updates
a

ticket, the scrip does not trigger. If a non-owner updates the ticket,
the

owner gets an update.

Looking into this more, if any watcher updates the ticket, that watcher
(owner, admin) doesn’t get the update, regardless of the scrip action.

Is this the “new way” for rt3? Or a bug?


matthew zeier | “Nothing in life is to be feared.
InteleNet Communications, Inc. | It is only to be understood.”
(949) 784-7904 | - Marie Curie


rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel


http://www.bestpractical.com/rt – Trouble Ticketing. Free.


rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

http://www.bestpractical.com/rt – Trouble Ticketing. Free.

My productoin rt2 has:

@{ $self->{‘To’} } = grep ( !/^$creator$/, @To );
@{ $self->{‘Cc’} } = grep ( !/^$creator$/, @Cc );
@{ $self->{‘Bcc’} } = grep ( !/^$creator$/, @Bcc );
@{ $self->{‘PseudoTo’} } = @PseudoTo;

in Notify.pm.

I’ll accept that my install was somehow changed, but it’s not at all clear
to me where. The obvious files don’t show any diffs when compared to the
default files.From: “Jesse Vincent” jesse@bestpractical.com
To: “matthew zeier” mrz@intelenet.net
Cc: rt-devel@lists.fsck.com
Sent: Friday, March 07, 2003 3:42 PM
Subject: Re: [rt-devel] notify owner issues, 2.1.83

http://www.fsck.com/rtfm/article.html?id=5#73

Seriously? I’ve done two seperate RT2 installs and both behave the
same.

OnTransaction NotifyOwner with template Transaction

I diff’d Notify.pm from a fresh download of rt2.0.15 and what I have
installed and it came out the same. Did the same for AnyTransaction.pm,
same thing.

Where would some local user (me) have altered RT?

  • mz

----- Original Message -----
From: “Jesse Vincent” jesse@bestpractical.com
To: “matthew zeier” mrz@intelenet.net
Cc: rt-devel@lists.fsck.com
Sent: Friday, March 07, 2003 3:26 PM
Subject: Re: [rt-devel] notify owner issues, 2.1.83

This is how RT2 and RT3 have always been. It is not a change.
If your RT2 does something different, a local user has altered RT’s
code.

I’m still having issues on this notify owner scrip. If an owner
updates

a

ticket, the scrip does not trigger. If a non-owner updates the
ticket,

the

owner gets an update.

Looking into this more, if any watcher updates the ticket, that
watcher

(owner, admin) doesn’t get the update, regardless of the scrip
action.

Is this the “new way” for rt3? Or a bug?


matthew zeier | "Nothing in life is to be
feared.

InteleNet Communications, Inc. | It is only to be
understood."

(949) 784-7904 | - Marie Curie


rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel


http://www.bestpractical.com/rt – Trouble Ticketing. Free.


rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel


http://www.bestpractical.com/rt – Trouble Ticketing. Free.