
Hi, I am trying to create a user which has all the permissions except changing the owner of the tickets in that queue but even I give all the privileges except 'rw' this user can't see that queue and the tickets in it. If I give rw it can see the queue and the tickets but the user can also change the owner of the tickets ofcourse. Is this a bug? Thanks Erol YILDIZ -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

On Thu, 07 Oct 2004 10:09:58 +0300, Erol YILDIZ
Hi,
I am trying to create a user which has all the permissions except changing the owner of the tickets in that queue but even I give all the privileges except 'rw' this user can't see that queue and the tickets in it. If I give rw it can see the queue and the tickets but the user can also change the owner of the tickets ofcourse.
Add the following to your Config.pm # QueueViewAllPossibleTickets # (show all ro and rw queues - not just rw queues) $Self->{QueueViewAllPossibleTickets} = 1; One thing to be aware of though. Take away owner will make it so that they can't change owner, but it will also make it so the agent can't be an owner either. They won't be able to claim and work on tickets! I had this same problem and learned the hard way. We have just made it an institutional procedure that only a supervisor can change owners. If an agent changes without express permission to do so, there can be disciplinary action. Hth, Tyler

Thanks for the reply. I need it to be that way because I will use OTRS just for 'internal customers'..
On Thu, 07 Oct 2004 10:09:58 +0300, Erol YILDIZ
wrote: Hi,
I am trying to create a user which has all the permissions except
changing
the owner of the tickets in that queue but even I give all the privileges except 'rw' this user can't see that queue and the tickets in it. If I give rw it can see the queue and the tickets but the user can also change the owner of the tickets ofcourse.
Add the following to your Config.pm
# QueueViewAllPossibleTickets # (show all ro and rw queues - not just rw queues) $Self->{QueueViewAllPossibleTickets} = 1;
One thing to be aware of though. Take away owner will make it so that they can't change owner, but it will also make it so the agent can't be an owner either. They won't be able to claim and work on tickets!
I had this same problem and learned the hard way. We have just made it an institutional procedure that only a supervisor can change owners. If an agent changes without express permission to do so, there can be disciplinary action.
Hth,
Tyler _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting f?r Ihr OTRS System? => http://www.otrs.de/

Hi, Anybody tried to use OTRS as an internal helpdesk system for a whole company? I mean for example if someone from accounting dep. has a request from IT dep. he send his request throug the web interface of OTRS, if someone from human resources dep. requests something from another department he sends a request from OTRS etc. Even if nobody uses OTRS for this aim, is it logical to use OTRS this kind? Thanks
participants (2)
-
Erol YILDIZ
-
Tyler Hepworth