Re: [otrs] "Next Ticket state" problem

:D funny On Tue, Jan 7, 2014 at 7:00 AM, Nick Bright wrote: > I don't know what made me think of it, but the problem was one of case > sensitivity. > > "Open" is not "open". > > the SysConfig parameters specify "open", but someone had changed the State > to "Open" at some point in the past. >

Re: [otrs] "Next Ticket state" problem

I don't know what made me think of it, but the problem was one of case sensitivity. "Open" is not "open". the SysConfig parameters specify "open", but someone had changed the State to "Open" at some point in the past. After changing the case to "open", when creating a new ticket, it default

Re: [otrs] "Next Ticket state" problem

I'm not sure I would call it a "bad entry", but the one that gets chosen by default (I think because it is simply alphabetically first) is a "closed" state type. On 1/6/2014 10:54 PM, Gerald Young wrote: What is the state type of the bad entry? On Mon, Jan 6, 2014 at 11:39 PM, Nick Bright

Re: [otrs] "Next Ticket state" problem

What is the state type of the bad entry? On Mon, Jan 6, 2014 at 11:39 PM, Nick Bright wrote: > Greetings, > > In our OTRS installation some years ago, we configured several custom > "close" states. > > Since then we have been putting up with (unable to solve) a problem where > ALL new tickets

[otrs] "Next Ticket state" problem

Greetings, In our OTRS installation some years ago, we configured several custom "close" states. Since then we have been putting up with (unable to solve) a problem where ALL new tickets want to start with a "Next Ticket State" of the first in the list of these custom close states. As you