Notify All != all watchers?

Argument “All” doesn’t appear to apply to the ticket owner. I’m not seeing
anything in the log trying to send to the ticket owner, although everyone
else gets updates.

Feature?

*************************** 10. row ***************************
id: 10
Name: Notify Requestors, Ccs and AdminCcs
Description: Send mail to all watchers
ExecModule: Notify
Argument: All
Creator: 1
Created: 2003-03-03 22:44:23
LastUpdatedBy: 1
LastUpdated: 2003-03-03 22:44:23
*************************** 11. row ***************************

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

matthew zeier wrote:

Argument “All” doesn’t appear to apply to the ticket owner. I’m not seeing
anything in the log trying to send to the ticket owner, although everyone
else gets updates.

Feature?

Yep. The “owner” isn’t necessarily a watcher. This is why the
scrip name has become

     Name: Notify Requestors, Ccs and AdminCcs

If you want to notify the owner, use the “Notify Owner” action.
�|� Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

matthew zeier wrote:

Argument “All” doesn’t appear to apply to the ticket owner. I’m not
seeing
anything in the log trying to send to the ticket owner, although
everyone
else gets updates.

Feature?

Yep. The “owner” isn’t necessarily a watcher. This is why the
scrip name has become

     Name: Notify Requestors, Ccs and AdminCcs

If you want to notify the owner, use the “Notify Owner” action.

What’s this for, then?

$arg =~ s/\bAll\b/Owner,Requestor,AdminCc,Cc/;

“Notify Owner” appears to limit the response to just Owner, while All
appears as though it should goto everyone, including Owner.

However, none of that matters since even “Notify Owner” tells me there
aren’t any recipients found.

However, none of that matters since even “Notify Owner” tells me there
aren’t any recipients found.

So. the Owner wouldn’t happen to be the person acting on the ticket,
would they?


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

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

However, none of that matters since even “Notify Owner” tells me there
aren’t any recipients found.

So. the Owner wouldn’t happen to be the person acting on the ticket,
would they?

Indeed, owner is the one acting on the ticket.

This behavior differs from rt2, however, or at least for my installation.
Owners get updates on all ticket updates, regardless of who made the update.

Pet peeve - why doesn’t ‘All’ expand to ‘OtherRecipients’ as well?

Granted it’s not too tricky to create a ‘NotifyEveryone’ scripaction, but
it does seem odd that ‘All’ isn’t in fact all.

John

J. Sloan wrote:

Pet peeve - why doesn’t ‘All’ expand to ‘OtherRecipients’ as well?

It peeved enough people that the action has now been redescribed as

Notify Requestors, Ccs and AdminCcs

:slight_smile:
�|� Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.