I have multiple locations with dedicated support staff. I want to use otrs as a single company wide ticket system.
What are some best-practice ways of segregating tickets by location?
It seems you could do different CIs, queues or location is a 'customer', but im looking for what has worked best for others.
Thanks
Tickets by location
Moderator: crythias
Tickets by location
OTRS 3.3.5 with LDAP auth for agent and customer
Windows 2008 R2
MySQL out of the box
Windows 2008 R2
MySQL out of the box
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Tickets by location
I haven't done it myself, but if I were to do so, top level queues being location would be what I'd do, with subqueues for each location as if they were top level queues.
Madrid::Printing <-> group Madrid
Madrid::Plumbing <-> group Madrid
Paris::Printing <-> group Paris
Paris::Plumbing <-> group Paris
and then potentially Regex ACL and/or groups/roles for appropriate Agents or customers per location.
CustomerGroupSupport enabled
CustomerA <-> group Madrid
AgentA <-> group Madrid
Madrid::Printing <-> group Madrid
Madrid::Plumbing <-> group Madrid
Paris::Printing <-> group Paris
Paris::Plumbing <-> group Paris
and then potentially Regex ACL and/or groups/roles for appropriate Agents or customers per location.
CustomerGroupSupport enabled
CustomerA <-> group Madrid
AgentA <-> group Madrid
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