[rt-users] Wishlist emails

[Roy El-Hames]

Hi ;

I have seen a couple of emails in the past a couple of months about wish 
list etc which I assume for a new major release, and I have a couple of 
wishes wondering if these can be looked into,

Ticket Merge/Unmerge:
As far as I can see, once 2 tickets are merged details about Requesters 
and individual tickets Cc 's are lost (ie which Requester/Cc for which 
ticket etc), my users (and I am sure many others) have merged tickets by 
mistake many times and for this I have created a function for them that 
unmerge tickets, however my function can't deal with the individual 
ticket requesters for the reason I mentioned above, any changes will 
need to be done in few places and wondering if the developers can look 
into cleaner way to merge and unmerge .. (If this is already there then 
please can some one correct me)

Content searching
I have tried many hacks to get an efficient content searching working, 
however with a 40G db mostly Attachment table (~ 22G in size) and 
Transactions table is not small either the content searching takes on 
average 15 minutes , we have a quad processor 3.8 GHz systems with 16G 
mem, the db is optimised, doing select * from Attachment where content 
like '%my search string%' returns in 5 minutes for the same query that 
may take over 15 minutes from the front end (and sometimes comes back 
with 0 tickets, my guess most the processing is building the join 
between Tickets, Transactions and Attachments, and I am wondering if the 
join can be eliminated:
    1- Adding smaller table of Ticket.id and Attachement.Id populated 
with every new attachement
    2- Take out Tickets table and use the Transactions.ObjectId as 
ticket Id's

In both of the above any customisation will take my RT far away from the 
base release and wondering if these are addressed in the new version , 
then I would rather wait.
I hope the above makes sense and looking forward to the new version.

Roy