What's the best method for reopening a ticket? I don't want notifications sent anywhere I just want the ticket set back to open status. Thank you, Jason Loven Manager - Technical Services Department Computer Associates, Inc. 36 Thurber Blvd, Smithfield RI 02917 Phone: (401)232-2600, Fax: (401)232-7778 Email: support@cainetserv.net Web: http://www.cainetserv.com/
The only way i could reopen an ticket was forwarding the message to my self and putting the status on "open" but there should be a beter way? right? Thomas Jason Loven wrote:
What’s the best method for reopening a ticket? I don’t want notifications sent anywhere I just want the ticket set back to open status.
Thank you,
Jason Loven
Manager - Technical Services Department
Computer Associates, Inc. 36 Thurber Blvd, Smithfield RI 02917 Phone: (401)232-2600, Fax: (401)232-7778 Email: support@cainetserv.net mailto:support@cainetserv.net
Web: http://www.cainetserv.com/
------------------------------------------------------------------------
_______________________________________________ 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 Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/
The only way i could reopen an ticket was forwarding the message to my self and putting the status on "open" but there should be a beter way?
right?
If you set the following config options, you can set the state of a ticket by adding a note: $Self->{'Ticket::Frontend::NoteSetState'} = 1; $Self->{'Ticket::DefaultNextNoteStateType'} = ['new', 'open', 'closed', 'removed']; The second is for specifying which states it can be set to. Regards, Richard
Begin forwarded message:
$Self->{'Ticket::Frontend::NoteSetState'} = 1; $Self->{'Ticket::DefaultNextNoteStateType'} = ['new', 'open', 'closed', 'removed'];
-- Christopher Mattogno Technology Specialist Hampshire Educational Collaborative 97 Hawley Street Northampton, MA 01060 p: 413.586.4900 x157 f: 413.586.0180 tmattogno@collaborative.org
participants (4)
-
Christopher Mattogno -
Jason Loven -
Richard Hinkamp - BeSite -
Thomas Wouters