one queue per agent
Moderator: crythias
one queue per agent
Running 3.3.8. Currently I have 4 techs under my lead. I would like for each of them to have their own queue that only they have access to. The tickets should come in to an "incoming" queue which they should all be able to see and move tickets to the correct agent/queue but once they are moved, they should not be visible anymore to the other techs. I've been reading through the docs but can't seem to get the permissions correct. If anyone can offer any tips I would appreciate it.
Re: one queue per agent
don't do personal queues. create them based on functional needs, so people can also work on other tickets if somebody gets ill or is on vacation
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: one queue per agent
jojo's right because it's a nightmare to maintain. But if you want to do it: add a queue and a queue group for each agent
all agents in triage group (where all tickets come in)
queue for main member of group triage
agentBob is a member of agentBob_grp and agentBobQueue is a member of agentBob_grp.
a hint on how to do this en masse: viewtopic.php?f=60&t=16933
The practical reason to do this is only if you promise you're not sharing tickets. Note that OTRS is designed to be more collaborative in this sense. Sharing knowledge of how tickets are solved is quite important.
all agents in triage group (where all tickets come in)
queue for main member of group triage
agentBob is a member of agentBob_grp and agentBobQueue is a member of agentBob_grp.
a hint on how to do this en masse: viewtopic.php?f=60&t=16933
The practical reason to do this is only if you promise you're not sharing tickets. Note that OTRS is designed to be more collaborative in this sense. Sharing knowledge of how tickets are solved is quite important.
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: one queue per agent
For right now that is what I want because my techs spend too much time pouring over others queues. I want them to focus on their queue and their queue only.jojo wrote:don't do personal queues. create them based on functional needs, so people can also work on other tickets if somebody gets ill or is on vacation
Re: one queue per agent
still is really bad design.
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
Re: one queue per agent
Do you have a good design that I could use to keep queues private?
Re: one queue per agent
there is no need to keep queues private.
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: one queue per agent
The only way to keep queues private is by group memebership. A queue is a member of exactly one group. An agent can be a member of multiple groups.
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: one queue per agent
I've done this and it works but the queues don't show up in my overview even though I have access to all groups. Any way to fix?
-
- Znuny guru
- Posts: 2210
- Joined: 13 Mar 2014, 09:16
- Znuny Version: 6.0.14
- Real Name: Rolf Straub
Re: one queue per agent
Did you select them in your preferences under "my queues" ?
Currently using: OTRS 6.0.14 -- MariaDB -- Ubuntu 16 LTS
Re: one queue per agent
Yes but that does not make them show up in "Ticket Queue Overview"
Re: one queue per agent
how will this show up in the report ?
i would like to explore this area too
i would like to explore this area too
otrs 3.3.8 OS windows 8 pro