I’m in the process of migrating a mysql-based RT installation to
postgresql (I’ll post a quick howto if it is of interest to someone).
Almost everything is working but I’m facing a small issue: rt-importer
correctly imports queues, tickets, attachments, scrips, … but doesn’t
keep the binding between scrips and queues.
For instance no scrip is “applied” in the Global section, and no scrip
is “applied” on queues.
I’m exporting from RT 4.2.2 and importing to the same version.
No error was reported during export with rt-serializer or import.
Almost everything is working but I’m facing a small issue: rt-importer
correctly imports queues, tickets, attachments, scrips, … but doesn’t
keep the binding between scrips and queues.
For instance no scrip is “applied” in the Global section, and no scrip
is “applied” on queues.
Thanks for your answer.
This ticket is about objectscrips not serialized. However, in my case, scrips are correctly exported and imported into my new DB, only the bindings are missing.
Another difference is that I’m running only version 4.2.2 of rt-serializer and rt-importer, and the reported ticket seems to refer to version 4.2.3! Note however that I’ve seen no changelog entry related to serializer/importer in version 4.2.3 so this can be a mistake in the ticket.
I believe you’re running into this Login
Thanks for your answer.
This ticket is about objectscrips not serialized. However, in my case, scrips are correctly exported and imported into my new DB, only the bindings are missing.
My mistake, this ticket is exactly about my problem, but I’m not used to
the mobile version of RT and didn’t read the history, just the summary.
I believe you’re running into this Login
Thanks for your answer.
This ticket is about objectscrips not serialized. However, in my case, scrips are correctly exported and imported into my new DB, only the bindings are missing.
My mistake, this ticket is exactly about my problem, but I’m not used to
the mobile version of RT and didn’t read the history, just the summary.
I’ll try the proposed patch then.
For anyone reading the archives, there is a second part of the patch
discovered during review.