Difference between "new" and "open" ticket
Moderator: crythias
Difference between "new" and "open" ticket
Anyone know the difference between a new and open ticket?
OTRS 3.1.6
-
- Znuny newbie
- Posts: 30
- Joined: 20 Apr 2011, 06:13
- Znuny Version: 3.0.11
- Real Name: Daniela Mahl
- Company: CONET Technologies AG
Re: Difference between "new" and "open" ticket
a new ticket normaly comes in from the customer by webinterface or email
a ticket has the open state when an agent works on it
a ticket has the open state when an agent works on it
OTRS Version: 3.0.11
ITSM 3.0.5
Betriebsystem: SLES 11
Apache2/MySQL 5
ITSM 3.0.5
Betriebsystem: SLES 11
Apache2/MySQL 5
Re: Difference between "new" and "open" ticket
Thanks.dma976 wrote:a new ticket normaly comes in from the customer by webinterface or email
a ticket has the open state when an agent works on it
OTRS 3.1.6
Re: Difference between "new" and "open" ticket
I noticed that Locking a ticket does not change it's state from New to Open.
Is this by design? Agent locking a ticket means he/she is working on it, correct?
If yes, then a ticket should not stay in the "new" state.
Is this by design? Agent locking a ticket means he/she is working on it, correct?
If yes, then a ticket should not stay in the "new" state.
RHEL 5.8
/ OTRS 3.2.0beta2 / SystemMonitoring

Re: Difference between "new" and "open" ticket
Agreed. It seems the ticket only changes from "new" to "open" is if the note is added with the "open" set to "next state"... At least so far from what I've done.solefald wrote:I noticed that Locking a ticket does not change it's state from New to Open.
Is this by design? Agent locking a ticket means he/she is working on it, correct?
If yes, then a ticket should not stay in the "new" state.
OTRS 3.1.6
Re: Difference between "new" and "open" ticket
Ah! Found a solution!altjx wrote:Agreed. It seems the ticket only changes from "new" to "open" is if the note is added with the "open" set to "next state"... At least so far from what I've done.solefald wrote:I noticed that Locking a ticket does not change it's state from New to Open.
Is this by design? Agent locking a ticket means he/she is working on it, correct?
If yes, then a ticket should not stay in the "new" state.
under Ticket -> Core::Ticket, enable Ticket::EventModulePost###130-ForceStateChangeOnLock
Credit: http://www.mail-archive.com/otrs@otrs.org/msg29144.html
RHEL 5.8
/ OTRS 3.2.0beta2 / SystemMonitoring

Re: Difference between "new" and "open" ticket
Wow, nice! Thanks for that!solefald wrote:Ah! Found a solution!altjx wrote:Agreed. It seems the ticket only changes from "new" to "open" is if the note is added with the "open" set to "next state"... At least so far from what I've done.solefald wrote:I noticed that Locking a ticket does not change it's state from New to Open.
Is this by design? Agent locking a ticket means he/she is working on it, correct?
If yes, then a ticket should not stay in the "new" state.
under Ticket -> Core::Ticket, enable Ticket::EventModulePost###130-ForceStateChangeOnLock
Credit: http://www.mail-archive.com/otrs@otrs.org/msg29144.html
OTRS 3.1.6