Automated user lookup and mapping

When user identities in the source and target systems don't match during synchronization, the connector finds and maps those user IDs.

This feature is available from TeamForge connector 2.2. Although workarounds for non-matching user identities were available in earlier releases, the new capability helps deal with additional licensing costs and reduces manual intervention for user management and maintenance.
Here's an example of how automated user lookup and matching works. Let's say you are synchronizing data from HP ALM to TeamForge and create a new defect in HP Quality Center with the “assignedTo” field set to some Quality Center user ID. Before the defect gets synchronized, the connector gets the username for the defect and checks whether the user ID exists in TeamForge. For more information on this feature, see this blog post.