Notification, Notification(Event), Vs Autoreponse

Hi All, I have been using Autoresponse<>queue to automatically respond to customers when new tickets are created. My question is, how can I automatically notify customers when their tickets are closed/updated? I have gone through "Notification" and "Notification(Event)" - Which of these can be used as an automatically triggered response to an event and how? (I'm using otrs2.4.4) Michael

first of all you have to patch Ticket.pm (
http://bugs.otrs.org/show_bug.cgi?id=4257) otherwise you'll go crazy trying
to understand why notification doesn't works
On Fri, Oct 16, 2009 at 10:01 AM, Michael Mayaka
Hi All, I have been using Autoresponse<>queue to automatically respond to customers when new tickets are created. My question is, how can I automatically notify customers when their tickets are closed/updated? I have gone through "Notification" and "Notification(Event)" - Which of these can be used as an automatically triggered response to an event and how? (I'm using otrs2.4.4)
Michael
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/

Hi Michael,
I have created two event notifications, one of which informs a user when
their case is closed, and the other when a note has been added to their
ticket (Note-External)
To configure a notification for a closed ticket, configure a
Notification(Event) as so: (if not specified, leave as blank)
Recipient : Customer
Event : TicketStateUpdate
State : Closed successful / Closed unsucsessful
Enter you desired subject and text. For mine its:
Hi All, I have been using Autoresponse<>queue to automatically respond to customers when new tickets are created. My question is, how can I automatically notify customers when their tickets are closed/updated? I have gone through "Notification" and "Notification(Event)" - Which of these can be used as an automatically triggered response to an event and how? (I'm using otrs2.4.4)
Michael
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/

Hi David, thanks for your step-by-step solution BUT the notifications aren't being sent out (The Auto-response works perfectly fine)
I have done the following:
1. Updated Ticket.pm from v 1.412 to v 1.416
2. Selected the following on Admin=>Notification (Event):
Recipient : Customer
Event : TicketStateUpdate
State : Closed successful / Closed unsucsessful
Subject: Ticket Closed! [

I think that you have to deselect states because it consider otherwise the
presents state of the ticket not the future state
On Fri, Oct 16, 2009 at 12:04 PM, Michael Mayaka
Hi David, thanks for your step-by-step solution BUT the notifications aren't being sent out (The Auto-response works perfectly fine) I have done the following: 1. Updated Ticket.pm from v 1.412 to v 1.416 2. Selected the following on Admin=>Notification (Event): Recipient : Customer Event : TicketStateUpdate State : Closed successful / Closed unsucsessful Subject: Ticket Closed! [
]( ) Text: Hi , Your ticket has been resolved by the support team as follows: (IT Helpdesk) Any idea on what I could be doing wrong?
Michael
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/

Hi Michael,
Are the event notifications marked as valid?
Try and create a test ticket, close it, and then view your syslog and post
the results.
Regards,
David
On Fri, Oct 16, 2009 at 11:04 AM, Michael Mayaka
Hi David, thanks for your step-by-step solution BUT the notifications aren't being sent out (The Auto-response works perfectly fine) I have done the following: 1. Updated Ticket.pm from v 1.412 to v 1.416 2. Selected the following on Admin=>Notification (Event): Recipient : Customer Event : TicketStateUpdate State : Closed successful / Closed unsucsessful Subject: Ticket Closed! [
]( ) Text: Hi , Your ticket has been resolved by the support team as follows: (IT Helpdesk) Any idea on what I could be doing wrong?
Michael
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/

Hi David,
Yes, the notification event is marked as valid; from Marco's advice, I've also tested with the "state" deselected but no notification is sent on ticket close. This is what is posted on the syslog when I create and close a ticket:
=============================================
Oct 16 13:53:03 appsvr1 OTRS-CGI-11[6798]: [Notice][Kernel::System::PostMaster::NewTicket::Run] Take UserLogin (imisdewcis) from customer source backend based on (imisdewcis@ital.co.ke).
Oct 16 13:53:03 appsvr1 OTRS-CGI-11[6798]: [Notice][Kernel::System::PostMaster::NewTicket::Run] Take UserCustomerID (imisdewcis@ital.co.ke) from customer source backend based on (imisdewcis@ital.co.ke).
Oct 16 13:53:03 appsvr1 OTRS-CGI-11[6798]: [Notice][Kernel::System::Ticket::TicketCreate] New Ticket [11013137/End-User Notifi] created (TicketID=718,Queue=IT Helpdesk,Priority=3 normal,State=new)
Oct 16 13:53:03 appsvr1 OTRS-CGI-11[6798]: [Notice][Kernel::System::Ticket::Article::ArticleSend] Sent email to 'imisdewcis@ital.co.ke' from 'IT Helpdesk

Hi All, The issue of notifications has now been fully solved by patching up to 2.4.5! Everything's running perfectly now. Thanks! Michael
participants (3)
-
David Holder
-
Marco Vannini
-
Michael Mayaka