A problem with Ticket Search

I am a begginer RT administrator, and we are using RT with our company’s user
support system. We have about 100000 or more e-mail addresses/users in RT
database at the moment, and trying to enter search engine, run simple
search or bulk update causes all of those e-mail addresses to load (which
takes approximately 20-30 minutes) before we can do anything. Is there any
way to configure RT not to load all of those data? I would appreciate any
help.
View this message in context: http://www.nabble.com/A-problem-with-Ticket-Search-tp21453763p21453763.html

I’m also having this issue. Does anyone know how to limit which users
show up in the Query Builder?

Thank you,
Micah Gersten
onShore Networks
Internal Developer

anusiak wrote:

I am a begginer RT administrator, and we are using RT with our company’s user
support system. We have about 100000 or more e-mail addresses/users in RT
database at the moment, and trying to enter search engine, run simple
search or bulk update causes all of those e-mail addresses to load (which
takes approximately 20-30 minutes) before we can do anything. Is there any
way to configure RT not to load all of those data? I would appreciate any
help.

That souunds you give right “OwnTicket” to all your users
(priveleged/unprivileged). You should review you’re permissions and
limit OwnTicket to your members of support teams.