Emmanuel Lacour schrieb:
> On Mon, Feb 02, 2009 at 05:03:26PM +0100, Christopher Kunz (Filoo GmbH) wrote:
>> Emmanuel Lacour schrieb:
>>> On queue with Id 33, you gave right OwnTicket to Group 5 and Group 5 is
>>> usually the "Unprivileged" group!
>> I
Emmanuel Lacour schrieb:
> On queue with Id 33, you gave right OwnTicket to Group 5 and Group 5 is
> usually the "Unprivileged" group!
I removed that privilege from the respective queue (it is a test queue
that was never actually used), and double-checked all other queues.
However, I found a coupl
Emmanuel Lacour schrieb:
>
> select * from ACL where RightName='OwnTicket';
>
mysql> select * from ACL where RightName='OwnTicket';
+--+---+-+---++--+-+---+
| id | PrincipalType | PrincipalId | RightName | ObjectT
kem cho schrieb:
> Check this out:
>
> http://www.gossamer-threads.com/lists/rt/users/81858#81858
>
Nice workaround, works fine for me. Owner change is very rarely used in
our setup, anyway.
Regards,
--ck
--
Christopher Kunz | Geschäftsführung | ch...@filoo.de
Filoo GmbH | Tilsit
Emmanuel Lacour schrieb:
> On Mon, Feb 02, 2009 at 01:33:19PM +0100, Christopher Kunz (Filoo GmbH) wrote:
>> Emmanuel Lacour schrieb:
>>> you seems to gave OwnTicket right to everyone or unprivileged users,
>>> check your permissions.
>> Any other ideas?
>>
Emmanuel Lacour schrieb:
> you seems to gave OwnTicket right to everyone or unprivileged users,
> check your permissions.
Currently, global Group Rights are as follows:
Everyone: CreateTicket
Privileged: ShowOutgoingEmail
Unprivileged: CreateTicket, ReplyToTicket, ShowOutgoingEmail, Watch
Request
Hi all,
since our upgrade to RT 3.6.4, the "resolve multiple tickets"
functionality shows erratic behavior in my installation. When before, it
only showed the privileged users (which are in the ballpark of 3-10 per
queue), it then started to show *all* users who ever submitted tickets,
including o
