Hi all, I don't know if there's any MasterSlave list or forum going on, so I've decided to send this here. Sorry if it's not convenient and gladly would receive any URL or email to post or send this email to. We are currently using OTRS 3.0 on our production environment and I'm testing OTRS 3.1 upgrade on a test system (with production data). I've been having problems with MasterSlave upgrade. I've followed the steps in http://forums.otterhub.org/viewtopic.php?f=60&t=15497, but they didn't seem to work for me, so I'll tell the problems I had and how I solved them: - Dynamic Field was not properly upgraded: there is a Dynamic Field created by the OTRS 3.1 upgrade script, called 'TicketFreeText12', named 'MasterSlave', but it was invalid and didn't match value in MasterSlave::DynamicField + Solved via SQL, because there was a problem defining an empty Possible Value via Sysconfig. + UPDATE dynamic_field SET name='MasterSlave', label='MasterSlave', valid_id=1 WHERE id='24'; - Old Master Slave relations (those created in 3.0 environment) were no longer recognized. + It seemed to be because the dynamic field value of the slaved ticket now stores the ticketnumber of the master ticket. + I've solved using the attached script. It will gather all the old slave ticket and try to re-slave them to the first target of a Parent-Child link which happens to be a Master Ticket. + I know is not a perfect solution, but we don't have much links between tickets, most slave tickets have just one Parent-Child relation and, of those that have more than one Parent-Child relation, normally only one of them would be master, so it pretty much keeps everything together. + Of course, if you have this problem, your situation may vary and you should customize and test in a test environment before applying to a production system. Kind regards, Juan Clavero