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 |
Please take further conversation to the list.
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.
State ⇒ Rejected
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.
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.
regular listeners, instead of automatically overriding it?
State ⇒ Assigned
New Attachment: Ticket.php.patch
wasn't 100% sure how it should be done.
Thanks.
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Ticker::notify() Anyone
Queue ⇒ Whups
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!