[rt-users] RT2-to-RT3 migration lost ticket data and status change issues
brian.friday at gmail.com
Wed Dec 31 16:11:17 EST 2008
On Dec 31, 2008, at 10:45 AM, Kevin Falcone wrote:
> On Dec 18, 2008, at 9:01 PM, Brian Friday wrote:
>> Thanks Drew,
>> Your tips led me to the library issues. RT2 can not be exported
>> without the same perl modules used for RT2. Once I installed the
>> correct libraries everything exported correctly.
>> My import however still has one snag, or rather 51,000 or so snags. I
>> have 51,000 tickets with the status of "new" 99% of which did not
>> originally have that status when they were exported and did not have
>> that status in the dump file.
> You didn't say what version of RT-Extension-RT2toRT3 you're
> using, but I've done numerous rt2 to rt3 conversions using
> the cpan versions without seeing this
> If Status isn't making it into the dumpfiles generated by rt-2.0-to-
> then they will default to 'new' when being created by in rt3
Actually I did, latest, though I guess I could be more clear and said
SVN version as well.
The status exists in the dumped tickets but that status is not
maintained in the dumpfile to rt3
push rather all resolved tickets are pushed back to new a status we
did not have in RT2.
More information about the rt-users