[Tickets #956] Ticket::notify() Anyone

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=956
-----------------------------------------------------------------------
 Ticket     | 956
 Updated By | mbydalek at mobilemini.com
 Summary    | Ticket::notify() Anyone
 Queue      | Whups
 State      | Assigned
 Priority   | 1. Low
 Type       | Enhancement
 Owners     | 
-----------------------------------------------------------------------


mbydalek at mobilemini.com (2004-12-09 06:17) wrote:

My initial response to your comment was "No because in certain cases you may
not want to constantly notify them, just on certain conditions, ie. when a
ticket is created, or just when a ticket is closed, etc." 

But then I looked at the code, and thought that both are actually a good
idea.  What if somehow you could choose to permanently add an e-mail address
to listen to a certain Queue, type or state in the configuration, but then
also hard-code certain notifications in the code?

So for example, you hard-code to send an e-mail to <a at a.com> only when a
ticket is created**, because that's all they care about - just the initial
information.  But then you can also code in <b at a.com> to listen to tickets
matching certain criteria?

It'd be a lot of work, but it might be worth it.

Thoughts?

** The reason why I have this case is for our HR dept.  Basically whenever
an employee position changes (new hire, promotion, termination, etc) certain
people need to be notified.  Well, all they care about is the initial e-mail
which contains all the person's information and don't need to be permanent
listeners.