RT2 to RT3 user import problems

Hi folks,

I’m migrating an old RT 2.0.7 installation to RT 3.2.2 and we’ve pretty
much got it working (with some homegrown hackery to ease the migration)
except for one thing: some user accounts are being mangled by the
importer.

The root cause appears to be that somehow, RT 2.0.7 allows multiple
tuples in the users table to contain the same e-mail address, and
sometimes with different case, for example:

rt2=> select name, emailaddress from users where emailaddress like
’Michael_Douglas%’;
name | emailaddress
douglasm | Michael_Douglas@CBC.CA
Michael_Douglas@CBC.CA | Michael_Douglas@CBC.CA

Subsequently, when the dumpfile-to-rt-3.0 script runs, it seems to
prioritize the user import based on the e-mail address:

rt3=> select name, emailaddress from users where emailaddress like
’Michael_Douglas%’;
name | emailaddress
Michael_Douglas@CBC.CA | Michael_Douglas@CBC.CA
(1 row)

rt3=> select name, emailaddress from users where name = ‘douglasm’;
name | emailaddress
(0 rows)

This is very bad, because the user logs in using the “douglasm” user ID
and it’s gone (and the attribution of tickets to that person are lost).

Is there any way to fix this, either in the importer, or otherwise?

  • Julian

– Julian C. Dunn, B.A.Sc, P.Eng. Julian_Dunn@cbc.ca
– Platform Administrator, CBC.ca Production & Operations
– Office: 2C310-Q * Tel.: (416) 205-3311 x5592