P4DTI issue job000108

TitleUserids can't differ between TeamTrack and Perforce
Assigned userGareth Rees
DescriptionThe TeamTrack integration assumes that users have the same userids in Perforce and TeamTrack. So the replication will fail when they differ.
AnalysisA good strategy when userids differ is to use e-mail addresses to pair up users, as in the Bugzilla integration.
But how will the automatic configuration engine pick which strategy to use for matching userids?
RB says: we'll match up by e-mail address by default. Any users not matched will just be replicated as before (as themselves).
How foundinspection
EvidenceWe saw this problem at Quokka and hacked up a user mapper (in config_teamtrack.py in the Quokka branch), but with the new translator architecture that hack will no longer work.
Created byGareth Rees
Created on2000-11-30 16:44:49
Last modified byGareth Rees
Last modified on2001-12-10 19:07:31
History2000-11-30 GDR Created. Agreed priority with RB.


Change Effect Date User Description
5624 closed 2000-12-07 13:59:19 Gareth Rees Tell admin to restart the replicator when adding new users to TeamTrack or changing their userids or e-mail addresses.
5623 closed 2000-12-07 13:57:35 Gareth Rees Matching users by e-mail address in the TeamTrack integration:
Created new class dt_perforce; a placeholder for an eventual full implementation of a defect_tracker subclass that interfaces to Perforce. One of its member variables is a p4 object; this means that the user_translator can se it to interface to Perforce and get the email addresses of the users.
Updated user_translator so that it matches users by e-mail address if it can; otherwise it defaults to the original algorithm: assume that they are identical.
Documented the need to have the same e-mail addresses or userids in the AG.