How to hide one queue in customerticketmessage.dtl

Moderator: crythias

Locked
tomekliw
Znuny newbie
Posts: 32
Joined: 02 Dec 2010, 11:17
Znuny Version: 3
Location: Poland

How to hide one queue in customerticketmessage.dtl

Post by tomekliw »

Hi,

I had 4 queues, but I want to hide one of them in customerticketmessage.dtl but only from part of customers.

I mean that all customers should see status and content of ticket from all 4 queues and should be able to create ticket only in 3 of them. So far so easy but, there are some customers, who could create tickets in this 4th queue. ho to do it?

Help please.
OTRS 3.1.10 on CentOS and MySql. Auth for customers and agents via both Active Directory and local database.
yuri0001
Znuny superhero
Posts: 630
Joined: 17 Mar 2011, 14:40
Znuny Version: 5.0.6
Real Name: Yuri Kolesnikov
Location: Russia

Re: How to hide one queue in customerticketmessage.dtl

Post by yuri0001 »

Hi!
Try to see in AdminArea - Customer<-->Group Relations. There you can assign -RO or -RW rights in Groups (queues) :?
Best regards Yuri Kolesnikov
OTRS 5.0.14, ITSM 5.0.14
SUSE 13.2, MariaDB 10.0.22(productive)
OTRS 5.0.14, ITSM 5.0.14(test)
Sanchez
Znuny newbie
Posts: 7
Joined: 06 May 2011, 10:05
Znuny Version: 3.0.7
Real Name: Patryk

Re: How to hide one queue in customerticketmessage.dtl

Post by Sanchez »

If you have queue attached to specific group, then Customer<-->Group Relations should do it as yuri0001 stated.
Set RO to every client and RW with RO for customers which can create ticets for 4th queue.
OTRS 3.0.8, openSUSE 11.4, Apache 2.2.17, PostgreSQL 9.0.3
tomekliw
Znuny newbie
Posts: 32
Joined: 02 Dec 2010, 11:17
Znuny Version: 3
Location: Poland

Re: How to hide one queue in customerticketmessage.dtl

Post by tomekliw »

This is right what You said, but I want every customer have rw permission to group connected with queue (and it's done by default group), but only some of them shoud see this queue in "To: " field in new ticket form.
OTRS 3.1.10 on CentOS and MySql. Auth for customers and agents via both Active Directory and local database.
Locked