Hi, I’ve rerun the test install twice: -I’ve tried uninstalling MasterSlave, then OTRS 3.1 upgrade and then OTRSMasterSlave install: this didn’t work because DATABASE MIGRATION SCRIPT didn’t create Dynamic Field TicketFreeText12 as a dropdown, instead it was a text and you couldn’t change it, although it migrated the ticket data correctly. - I’ve tried OTRS 3.1 upgrade, uninstall MasterSlave and install OTRSMasterSlave. Data is correctly migrated and TicketFreeText12 is created as a dropdown, although is not named neither labeled MasterSlave and it remains as invalid. Once I’ve renamed and validated, it works for new tickets, but it doesn’t recognize Master-Slave relations in 3.0 Tickets… So, it seems OTRSMasterSlave install is not working for me… anyone has any clue as to why it may be failing? Kind regards, Juan Clavero De: Juan Manuel Clavero Almirón [mailto:juanm.clavero@ibsalut.es] Enviado el: jueves, 16 de agosto de 2012 14:59 Para: otrs@otrs.org Asunto: [otrs] problem installing OTRSMasterSlave Hi all, In my test installation, OTRSMasterSlave didn’t rename TicketFreeText12 dynamic field to MasterSlave and didn’t set it as valid. Some things were not working as I expected until I realized this was the origin. Is it a normal behaviour of the installation? I followed the steps in http://forums.otterhub.org/viewtopic.php?f=60&t=15497 and the video linked Kind regards, Juan Clavero