[rt-users] Re: BUG in rt2->rt3 conversion re: keywords

[Nicolae P. Costescu]

I was able to straighten the keywords out with a lot of SQL gymnastics. 
Basically I had to create new CustomFields, then new CustomFieldValues, 
then map all the customfields from the TicketCustomFieldValues to the new 
CustomFields. Then I disabled the queue specific custom fields for every 
queue except 0 (global), except for the queues that really were supposed to 
have queue specific custom fields (whew).

Now I'm left with a bunch of duplicate custom fields, and I'm finding it 
hard to remove duplicates with mysql's limitations (no views,no functions, 
no subselects). So I'm writing a C program to do it. I thought about 
importing the table into postgres and doing it there...

Remember - the issue is not that you can't keep keywords when moving from 
queue to queue.

The issue is that the rt2->rt3 upgrade script takes your global keywords 
from rt2 and replicates them as queue specific keywords in every queue in rt3!

Ouch.

At 03:36 PM 4/14/2003 -0400, Alexander Dupuy wrote:
>Nicolae P. Costescu wrote:
>>In my rt2 database I had only global keywords.
>>In my rt3 database they are now queue specific, and exist in every queue. 
>>So when we move tickets from one queue to another they lose the keyword 
>>settings (though the keyword selection lists are there because the 
>>conversion program created them in every queue).
>>Is there any way to fix this now that I have those custom fields/keywords 
>>in every queue instead of globally?
>
>I too would be interested in knowing if there is a way to keep keyword 
>values when moving tickets from queue to queue in rt3.  Our workflow 
>is   quite dependent on moving tickets, and we are using keywords heavily, 
>so it would be kind of a showstopper for us if there's no way to do this 
>with rt3.
>
>There's at least one other RT user who also feels this way -- his was the 
>only reply when I asked about this problem last November 
>(http://lists.fsck.com/pipermail/rt-users/2002-November/010685.html) -- 
>but nobody provided any pointers on how to preserve the keyword values.
>
>@alex
>--
>mailto:dupuy at sysd.com
>

****************************************************
Nicolae P. Costescu, Ph.D.  / Senior Developer
Stronghold Technologies
46040 Center Oak Plaza, Suite 160 / Sterling, Va 20166
Tel: 571-434-1472 / Fax: 571-434-1478