RE: [otrs] TicketHook Issue after upgrade to 2.0.1

2005-08-19 Thread West, Bradley G.
Title: RE: [otrs] TicketHook Issue after upgrade to 2.0.1 I haven't heard about a list but from what I'm seeing a lot of things have simply been broken down into their component structures TicketHook becomes Ticket::Hook TicketNumberGenerator becomes Ticket::Numbe

Re: [otrs] TicketHook Issue after upgrade to 2.0.1

2005-08-19 Thread Moritz Bunkus
Hey, On Thursday 18 August 2005 15:46, West, Bradley G. wrote: > The new format in 2.0.1 is > > $Self->{'Ticket::Hook'} = 'Your Ticket Hook String Here'; Is there a list that maps all or at least some of the old configuration options to the new ones? Or at least a list of the new options? UPG

RE: [otrs] TicketHook Issue after upgrade to 2.0.1

2005-08-18 Thread West, Bradley G.
Title: Message The new format in 2.0.1 is       $Self->{'Ticket::Hook'} = 'Your Ticket Hook String Here'; From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul O'Neill - ValistaSent: Thursday, August 18, 2005 9:40 AMTo: otrs@otrs.orgSubject: [

[otrs] TicketHook Issue after upgrade to 2.0.1

2005-08-18 Thread Paul O'Neill - Valista
Title: Message Hi,    I upgraded from 1.3 to 2.0.1, there were a couple of small database issues that I had to fix but all seemed fine. However the one thing I cannot fix is the TicketHook. Here is my setting in $OTRS_HOME/Kernel/Config.pm:   Self->{'TicketHook'} = 'Call ID#: ';   However all