Hi
I would like to assign automatically a ticket responsible per queue. Is it possible? I search within generic agent area, but witout success.
Best regards,
Hugo
mod note: changed title due to misspelling -- crythias
Assign ticket responsible
Moderator: crythias
Re: Assign ticket responsible
I can think of a solution for your problem:
In the SysConfig there is a configuration called Ticket::ResponsibleAutoSet, if you set this and Ticket::Responsible to "Yes" you can create a new job for the generic agent, using a queue as filter ticket and a new owner as action. This will automatically set an agent as owner and responsible for the tickets within a queue.
I hope this helps!
Regards,
Elva
In the SysConfig there is a configuration called Ticket::ResponsibleAutoSet, if you set this and Ticket::Responsible to "Yes" you can create a new job for the generic agent, using a queue as filter ticket and a new owner as action. This will automatically set an agent as owner and responsible for the tickets within a queue.
I hope this helps!
Regards,
Elva
-
- Znuny newbie
- Posts: 84
- Joined: 27 Jan 2011, 22:10
- Znuny Version: 5.0.x
- Company: AnyWeb AG
- Location: Zürich, Switzerland
Re: Assign ticket responsible
Hi Hugo
I want to do exactly the same thing as you. Set automatically a ticket responsible per queue. And I also miss the possibility to set the responsible with generic agent.
Did you solve this?
The suggested solution of Elva does not help. I dont want to have same owner and responsible per ticket.
Best regards,
Christof
I want to do exactly the same thing as you. Set automatically a ticket responsible per queue. And I also miss the possibility to set the responsible with generic agent.
Did you solve this?
The suggested solution of Elva does not help. I dont want to have same owner and responsible per ticket.
Best regards,
Christof
OTRS 5.0.x, CentOS 6.6, MariaDB 10.1.20
Re: Assign ticket responsible
This is not good practice. Why would you force feed someone responsibility?cmadoery wrote:Hi Hugo
I want to do exactly the same thing as you. Set automatically a ticket responsible per queue. And I also miss the possibility to set the responsible with generic agent.
Shawn Beasley
Contact me per XING
Contact me per LinkedIN
OTRS CVS on Ubuntu Stable.

signature by diginin74, on Flickr
Computers are like air conditioners, when you open windows they are useless.
P.S. (für Leser meiner Deutschtexte) Rechtschreibfehler bitte mit s/.*/$KORREKTUR/ ersetzen.
Contact me per XING
Contact me per LinkedIN
OTRS CVS on Ubuntu Stable.

signature by diginin74, on Flickr
Computers are like air conditioners, when you open windows they are useless.
P.S. (für Leser meiner Deutschtexte) Rechtschreibfehler bitte mit s/.*/$KORREKTUR/ ersetzen.
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Assign ticket responsible
Probably for the same reason one would force feed an agent to be owner of a ticket? (ie: one dispatch/observer/watcher, one person who would actually handle the ticket).diginin wrote:This is not good practice. Why would you force feed someone responsibility?
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: Assign ticket responsible
I guess it might be the same, it is a question of theological nature. Anyway, it is not currently passible. Maybe someday.crythias wrote:Probably for the same reason one would force feed an agent to be owner of a ticket? (ie: one dispatch/observer/watcher, one person who would actually handle the ticket).diginin wrote:This is not good practice. Why would you force feed someone responsibility?
Shawn Beasley
Contact me per XING
Contact me per LinkedIN
OTRS CVS on Ubuntu Stable.

signature by diginin74, on Flickr
Computers are like air conditioners, when you open windows they are useless.
P.S. (für Leser meiner Deutschtexte) Rechtschreibfehler bitte mit s/.*/$KORREKTUR/ ersetzen.
Contact me per XING
Contact me per LinkedIN
OTRS CVS on Ubuntu Stable.

signature by diginin74, on Flickr
Computers are like air conditioners, when you open windows they are useless.
P.S. (für Leser meiner Deutschtexte) Rechtschreibfehler bitte mit s/.*/$KORREKTUR/ ersetzen.
-
- Znuny newbie
- Posts: 84
- Joined: 27 Jan 2011, 22:10
- Znuny Version: 5.0.x
- Company: AnyWeb AG
- Location: Zürich, Switzerland
Re: Assign ticket responsible
Some agents are part time workers. And we do have sort of supervisors for all tickets in some queues. For example repair-queue for some products. Supervisor is not always the same person for a queue. It's more a role. So on Monday I'm SV for Queue A, on Tuesday you are SV for queue A and so one. I Know its not exactly ITIL compliant, but it works for us.diginin wrote:
This is not good practice. Why would you force feed someone responsibility?
Do you have a suggestion to solve that? I could exchange the role of Responsible and Owner for example. Or do some scripting around that...
any ideas?
Christof
OTRS 5.0.x, CentOS 6.6, MariaDB 10.1.20
-
- Znuny newbie
- Posts: 84
- Joined: 27 Jan 2011, 22:10
- Znuny Version: 5.0.x
- Company: AnyWeb AG
- Location: Zürich, Switzerland
Re: Assign ticket responsible
Sorry to come back again with this. But what about using an event for that?
Like Edit Config Settings in Ticket -> Core::Ticket
Ticket::EventModulePost###140-ResponsibleAutoSet
and than (I just guess here)....
Event = TicketQueueUpdate
Module = Kernel::System::Ticket::Event::ResponsibleAutoSet
<Queue 1> = <Responsible 1>
<Queue 2> = <Responsible 2>
don't know if something like that could work out.
Christof
Like Edit Config Settings in Ticket -> Core::Ticket
Ticket::EventModulePost###140-ResponsibleAutoSet
and than (I just guess here)....
Event = TicketQueueUpdate
Module = Kernel::System::Ticket::Event::ResponsibleAutoSet
<Queue 1> = <Responsible 1>
<Queue 2> = <Responsible 2>
don't know if something like that could work out.
Christof
OTRS 5.0.x, CentOS 6.6, MariaDB 10.1.20