[rt-users] Query Builder Problems

[Chris Poupart]

Unfortunately, this hasn't brought me any closer to resolving the bug.

If I take a random auto-generated user,  they do not have "OwnTicket" 
rights on any of the queues. :(

So I then went through and removed all of the permissions to the system 
defined groups (Everyone, Privileged, Unprivileged, Owner, AdminCC, CC, 
etc) for all of the queues.

Now if I look at an unprivileged auto-created user in the Rights Matrix, 
they have "Create Ticket" rights to all of the queues, and "Watch" 
rights to all of the queues.  That's it.

However, I still have the problem that /all/ of the users load when I 
bring up the Build.html page. :-/

If anyone has any other advice on this one, I would love to hear it.

-- Chris

Chris Poupart wrote:
> Thanks Drew,
>
> I have RTx:RightsMatrix installed, and I am looking through.  So far 
> there is nothing obvious, unless I am missing something.
>
> I don't have an over-abundance of queues, so I may just go through 
> them and double-check the permissions for groups that would apply to 
> everyone (really only the default global groups).
>
> -- chris
>
> Drew Barnes wrote:
>> Somewhere, somehow, all of your users have "OwnTicket" rights.
>>
>> RTx::RightsMatrix can help you track this down.
>>
>>
>> Chris Poupart wrote:
>>  
>>> Hi All,
>>>
>>> I am in the process of upgrading our installation (and migrating to a
>>> new server) from 3.2.2 to 3.6.1.
>>>
>>> So far, I haven't had any problems, except for some performance issues
>>> with the Query Builder.
>>>
>>> Specifically, the behaviour for populating the drop down list for the
>>> "Owner" field in 3.2.2 is simply to list all the currently authorized
>>> users.  This limits you in that you can't search by people who have
>>> been deactivated, etc.
>>>
>>> In 3.6 (and i think even in 3.4) this behaviour was changed and the
>>> drop down is populated with ALL users, including deactivated users. 
>>> This is a huge performance hit for us as it loads a few thousand
>>> names.  Instead of the Build.html page loading in under a second, it
>>> takes roughly 20 seconds.  As well, with that many names in the
>>> dropdown, it is almost completely useless to use.
>>>
>>> I am unfortunately not much of a Perl hacker, and so I am not sure
>>> where to make the changes to fix this.  Ideally, I would love to
>>> replace the drop-down with a text field for free-form entry, but
>>> barring that, I would settle with returning the behaviour to the way
>>> that it is in 3.2.
>>>
>>> Any hints would be much appreciated.
>>>
>>> Thanks!
>>>
>>> Chris Poupart
>>> Network System Administrator
>>> Development, Alumni and University Relations
>>> McGill University
>>> _______________________________________________
>>> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>>>
>>> Community help: http://wiki.bestpractical.com
>>> Commercial support: sales at bestpractical.com
>>>
>>>
>>> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
>>> Buy a copy at http://rtbook.bestpractical.com
>>>     
>>
>>   
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> Buy a copy at http://rtbook.bestpractical.com