Hi all,
I'm looking at hiding a queue from all but a few agents and their respective customers. These users should still be able to place tickets into other queues but I basically don't want the business to be able to submit tickets into their queue as it will be used by the warehouse to manage their own work.
I've setup customer users using the UserLogin setting and know I need to set the Possible Change settings to Ticket > Queue = 'Warehouse' but whenever I do this I get two results neither of which are any good -
This is the only queue visible and the Warehouse queue is visible to everyone.
I would prefer not having to administer a white list of all queues for the warehouse and can't figure out how to restrict it from everyone. An ideal solution would be somthing like a not in statement i.e.
If CustomerUser > UserLogin is not in X, Y & Z then possible not Ticket > Queue = Warehouse. Is this even possible?
Thanks
Chris
Restrict Queues using ACL
Moderator: crythias
-
- Znuny newbie
- Posts: 40
- Joined: 17 Jul 2013, 11:09
- Znuny Version: 3.1.6
- Real Name: Chris
- Company: The Hut Group
Restrict Queues using ACL
OTRS 3.3.8 & KIX4OTRS 6.06 in both test and live. MySQL 5.1.52 on Red Hat Enterprise Linux Server release 6.0
-
- Znuny guru
- Posts: 2210
- Joined: 13 Mar 2014, 09:16
- Znuny Version: 6.0.14
- Real Name: Rolf Straub
Re: Restrict Queues using ACL
Negation isn't implemented yet (but I think will be in 4.0).
I'm using a regular expression with a negativ lookaround:
^((?!.*(name1|name2|name3)).*)$
Is this something you're looking for ?
I'm using a regular expression with a negativ lookaround:
^((?!.*(name1|name2|name3)).*)$
Is this something you're looking for ?
Currently using: OTRS 6.0.14 -- MariaDB -- Ubuntu 16 LTS
-
- Znuny newbie
- Posts: 40
- Joined: 17 Jul 2013, 11:09
- Znuny Version: 3.1.6
- Real Name: Chris
- Company: The Hut Group
Re: Restrict Queues using ACL
I'll give it a go but I think that looks similar to a regex I was already using. Good to know it may be in the pipeline although we will probably be hosted with a differnet solution by then.
I'll test later this week and feed back.
I'll test later this week and feed back.
OTRS 3.3.8 & KIX4OTRS 6.06 in both test and live. MySQL 5.1.52 on Red Hat Enterprise Linux Server release 6.0
-
- Znuny newbie
- Posts: 40
- Joined: 17 Jul 2013, 11:09
- Znuny Version: 3.1.6
- Real Name: Chris
- Company: The Hut Group
Re: Restrict Queues using ACL
Sorry about the delay. Just to let you know this works for Customers and I just need to test an agent config following the same process -
---
- ChangeBy: chris.machnicki
ChangeTime: 2014-11-06 11:30:30
Comment: A Queue Explicitly for the Warehouse IT Team
ConfigChange:
PossibleNot:
Ticket:
Queue:
- Warehouse IT
ConfigMatch:
Properties:
CustomerUser:
UserLogin:
- '[RegExp]^((?!.*(name1|name2|name3)).*)$'
CreateBy: chris.machnicki
CreateTime: 2014-11-03 17:15:42
Description: This should not be accessible to other customers
ID: 17
Name: Disallow Queue (Warehouse IT) for other customers
StopAfterMatch: 0
ValidID: 1
---
- ChangeBy: chris.machnicki
ChangeTime: 2014-11-06 11:30:30
Comment: A Queue Explicitly for the Warehouse IT Team
ConfigChange:
PossibleNot:
Ticket:
Queue:
- Warehouse IT
ConfigMatch:
Properties:
CustomerUser:
UserLogin:
- '[RegExp]^((?!.*(name1|name2|name3)).*)$'
CreateBy: chris.machnicki
CreateTime: 2014-11-03 17:15:42
Description: This should not be accessible to other customers
ID: 17
Name: Disallow Queue (Warehouse IT) for other customers
StopAfterMatch: 0
ValidID: 1
OTRS 3.3.8 & KIX4OTRS 6.06 in both test and live. MySQL 5.1.52 on Red Hat Enterprise Linux Server release 6.0
-
- Znuny newbie
- Posts: 40
- Joined: 17 Jul 2013, 11:09
- Znuny Version: 3.1.6
- Real Name: Chris
- Company: The Hut Group
Re: Restrict Queues using ACL
same config changing the CustomerUser to User -
---
- ChangeBy: chris.machnicki
ChangeTime: 2014-11-13 15:44:28
Comment: A Queue Explicitly for the Warehouse IT Team
ConfigChange:
PossibleNot:
Ticket:
Queue:
- Warehouse IT
ConfigMatch:
Properties:
User:
UserLogin:
- '[RegExp]^((?!.*(name1|name2|name3)).*)$'
CreateBy: chris.machnicki
CreateTime: 2014-11-13 15:37:20
Description: This should not be accessible to other agents
ID: 19
Name: Disallow Queue (Warehouse IT) for other agents
StopAfterMatch: 0
ValidID: 1
---
- ChangeBy: chris.machnicki
ChangeTime: 2014-11-13 15:44:28
Comment: A Queue Explicitly for the Warehouse IT Team
ConfigChange:
PossibleNot:
Ticket:
Queue:
- Warehouse IT
ConfigMatch:
Properties:
User:
UserLogin:
- '[RegExp]^((?!.*(name1|name2|name3)).*)$'
CreateBy: chris.machnicki
CreateTime: 2014-11-13 15:37:20
Description: This should not be accessible to other agents
ID: 19
Name: Disallow Queue (Warehouse IT) for other agents
StopAfterMatch: 0
ValidID: 1
OTRS 3.3.8 & KIX4OTRS 6.06 in both test and live. MySQL 5.1.52 on Red Hat Enterprise Linux Server release 6.0
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Restrict Queues using ACL
CustomerGroupSupportChrisMachnicki wrote:I'm looking at hiding a queue from all but a few agents and their respective customers.
Don't have agents or customers in the group attached to that queue.
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
-
- Znuny newbie
- Posts: 40
- Joined: 17 Jul 2013, 11:09
- Znuny Version: 3.1.6
- Real Name: Chris
- Company: The Hut Group
Re: Restrict Queues using ACL
I read into that but was trying to avoid the additional admin related to adding users to groups. It's a pretty basic setup when it comes to customers where everyone is added to the users group and no additional work is required afterwards.
Maybe that will help someone else looking though and it was a more obvious way of achieving this.
Thanks
Maybe that will help someone else looking though and it was a more obvious way of achieving this.
Thanks
OTRS 3.3.8 & KIX4OTRS 6.06 in both test and live. MySQL 5.1.52 on Red Hat Enterprise Linux Server release 6.0