Hello Gerald,
Thanks for the advice. I completely agree with you that the queue selection
shouln't relay in the type of the ticket. Customer should understand what
they are requesting an to who they are requesting it.
We have actually used your approach into some other implementation of OTRS,
but
Type isn't supposed to be used in that way, but you can try this:
http://forums.otterhub.org/viewtopic.php?f=60&t=8032
On Fri, Nov 2, 2012 at 10:13 AM, Alvaro Cordero wrote:
> Hello Carlos,
>
> We have tried that and other combinations, but still got nothing.
>
> Thank you.
>
> Regards
>
>
> 201
Hello Carlos,
We have tried that and other combinations, but still got nothing.
Thank you.
Regards
2012/11/1 Carlos Andrés Gallego Arboleda <
carlos.gall...@itconsultores.com.co>
> Hi Alvaro,
>
> You can try whit this line.
>
> Name => ['[RegExp]^1-Mesa'],
>
> Carlos Ga
Hi Alvaro,
You can try whit this line.
Name => ['[RegExp]^1-Mesa'],
Carlos Gallego
2012/11/1 Alvaro Cordero
> Hello Folks,
>
> I am using OTRS 3.0 and I am trying creating an ACL to define possible
> queues depending on the type selection.
>
> I have the following code
Hello Folks,
I am using OTRS 3.0 and I am trying creating an ACL to define possible
queues depending on the type selection.
I have the following code.
$Self->{TicketAcl}->{'ACL-Type-Queue'} =
{
Properties => {
Frontend => {
Action =>
['CustomerTick
