6.0.0-beta1
9/17/25

[#956] Ticket::notify() Anyone
Summary Ticket::notify() Anyone
Queue Whups
Type Enhancement
State Rejected
Priority 1. Low
Owners
Requester mbydalek (at) mobilemini (dot) com
Created 12/08/2004 (7588 days ago)
Due
Updated 12/13/2004 (7583 days ago)
Assigned 12/08/2004 (7588 days ago)
Resolved 12/11/2004 (7585 days ago)
Milestone
Patch No

History
12/13/2004 03:57:41 PM Chuck Hagenbuch Comment #7 Reply to this comment
whups/docs/TODO



Please take further conversation to the list.
12/13/2004 03:15:16 PM mbydalek (at) mobilemini (dot) com Comment #6 Reply to this comment
I see your point with everything as I was looking at it from just a 
Whups point of view, but it sounds like you are talking about the 
entire project.  Do you have a link or place where you keep the ToDo 
you referenced?  I tried to browse the site but didn't see anything.



I'd like to look at your idea of workflow and what all would be needed 
to implement it, mainly because it sounds like fun! :)



Thanks Chuck.
12/11/2004 05:05:51 AM Chuck Hagenbuch Comment #5
State ⇒ Rejected
Reply to this comment
This isn't going to be this simple. You need a way to call this extra 
parameter too, right? Which is another patch, or just another local 
mod. What you want is workflow, which is already on the todo list, but 
needs to be done thoroughly.
12/09/2004 02:17:18 PM mbydalek (at) mobilemini (dot) com Comment #4 Reply to this comment
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@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@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.
12/09/2004 12:37:12 AM Chuck Hagenbuch Comment #3 Reply to this comment
If we were to do this, shouldn't the $recipients argument add to the 
regular listeners, instead of automatically overriding it?
12/08/2004 08:46:40 PM Jan Schneider Summary ⇒ Ticket::notify() Anyone
State ⇒ Assigned
 
12/08/2004 08:29:20 PM mbydalek (at) mobilemini (dot) com Comment #2
New Attachment: Ticket.php.patch Download
Reply to this comment
I didn't properly format the function description at the top since I 
wasn't 100% sure how it should be done.



Thanks.
12/08/2004 08:27:58 PM mbydalek (at) mobilemini (dot) com Comment #1
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Ticker::notify() Anyone
Queue ⇒ Whups
Reply to this comment
Basically I'd like to add a parameter to the notify() function in 
Ticket.php to allow for notification of various people, and not just 
the listeners().  The reason for this could be that depending on a 
certain condition in a ticket, someone might need an e-mail.



In our situation, depending on a certain Subject, Queue, and State, we 
wanted to notify the HR department.  Well, the perfect thing to do 
would be send a copy of the initial e-mail, but I couldn't do that 
because only the listeners could be notified.   Hence my patch.



Let me know about thoughts ...



Thanks!

Saved Queries