Sorry, forgot the list. Kenn
On Tue, Jan 18, 2011 at 9:55 AM, Kenneth Crocker <[email protected]> wrote: > Todd, > > I'm thinking this AdminCc group has a whole bunch of Global rights. That > would do it. > > We did something similar but made it a bit more granular; we create a > Global Group for AdminCc but only gave them these rights; *AdminUsers, > AssignCustomFields, SeeCustomFields, SeeGroup, ShowConfigTab, ShowScrips, > ShowTemplates, WatchAsAdminCc*). Then we created an AdminCc group for each > set of Queues that belong to a specific Support Group (like Financial). > These AdminCc Sub-groups would be given rights *more specific to the > Queues they support*. This saves a lot of time when RT is searching for > user privileges per ticket. > > Global rights that involve Ticket privileges can be real time burners. > > Hope this helps. > > Kenn > LBNL > > > On Tue, Jan 18, 2011 at 9:43 AM, Todd Chapman <[email protected]> wrote: > >> RT Users, >> >> A few years ago we started adding a group as AdminCc to many tickets. >> It made sense for our process and seemed like a good idea at the time. >> Fast forward to today. This group is AdminCc on many, many tickets. >> Now when we add a new member to the group it can take 15 minutes for >> the add to complete, usually with the web interface timing out. >> >> To alleviate this situation I wrote a script to remove this group from >> many old tickets, but this too is taking a long time to complete. >> Here's the key line from the script: >> >> my ($status, $msg) = $t->DeleteWatcher(PrincipalId => $pid, Type => >> "AdminCc", Silent => 1); >> >> Which causes this long running mysql query: >> >> >> Command: Query >> Time: 86 >> State: Sending data >> Info: SELECT main.* FROM CachedGroupMembers main WHERE ((main.Via >> = '28522070')) AND ((main.id != '28522070')) >> >> >> Ouch. >> >> Can anyone recommend an approach to fixing this problem? >> >> Thanks. >> > >
