Hi Lukasz!! Thanks for the solution, I think it's a good possibility,
but if I test the code you sent me, when I choose in the customer
interface the queue selected in the ACLi can't see nothing in
'services', it's good because you see if it works just that for some
reason I can not see the
ITS WORKS!!
mi error era que cuando seleccionamos una sub-queue debemos colocar no
el nombre sino todo el árbol que le antecede, por ejemplo:
$Self-{TicketAcl}-{'nameOfACL'} = {
Properties = {
Queue = { Name = ['queue::subqueue1'], },
},
Possible = {
Ticket = {
This is possible by creating an ACL.
This will require you to add the following to /opt/otrs/Kernel/Config.pm
$Self-{TicketAcl}-{'nameOfACL'} = {
Properties = {
Queue = { Name = ['nameOfQueue'], },
},
Possible = {
Ticket = {
Service = ['Service 1',
there is no possibility to link the Service to Queue? is a bit annoying
to have the complete list of services and that nothing filter this ...
-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive:
Not really, because Queues are agnostic to Customers.
The only thing a Queue can be is a member of a group.
Customers can be members of a group.
Customers can be assigned services.
Services can be assigned SLAs.
The idea is that a Customer purchases a service, and with that service,
potentially
