[rt-users] Question about ticket bulk update

HI, I have RT 3.6.7 running on Postgresql 8.3 General performance was very poor, so we did some optimising last week. We added the following indices :- rtdb=# create index groups2_lower on groups(lower(type),instance,lower(domain)); rtdb=# create index users1_lower on users(lower(name));

[rt-users] Tickets created by junk mail

Hi, I was wondering what people on here think of being the best way to handle tickets automatically created by incoming junk mail. We get more than a fair few tickets created like this, and our support desk manager would like to be able to highlight these in some way so he can sort out his

[rt-users] Some searches produce tickets with incorrect links

Hi, I have successfully migrated my RT database from 3.6.7 to 4.0.7 on Debain Wheezy and Postgresql 9.2. Everything is looking good with the exception of the following problem I have found. If I do a search with the following criteria in the New Search query builder screen, then I get a

[rt-users] Problems upgrading from 3.9.3

HI, I am in the process of migrating my current RT to a brand new separate server running Debian/Postgresql and RT 4.0.7 installed via backports. I have managed to import the dump of the database into the new system, and have set about upgrading the database. I already have RT4.0.7 working

[rt-users] Migration to a new server

Hi, I have inherited an RT 3.6.7 system with around 300,000 tickets in it, taking up about 40GB of disk space. The hardware this runs on is getting on a bit, and response times are now getting to the frustratingly slow point. I have a new server (Debian Squeeze) on which I have managed to

[rt-users] Question regarding full text indexing with Postgresql

I have a question that needs an answer before I implement full text indexing on our new RT4 installation. Will Postgresql index just text, or does it try to index attachments as well ? I only want text from tickets to be indexed ideally. I intend to follow the instructions on the wiki page: