Map user list fields

Note: This topic is relevant for NextGen Synchronizer only. For details about the ALM Synchronizer, see ALM Synchronizer for Agile Manager or search using the ALM Synchronizer filter.

Agile Manager and ALM maintain separate lists of user list fields, such as for the Assigned To field.

Users in these lists are mapped once for each pair of endpoints. This means that if you mapped the users between an Agile Manager workspace and an ALM project when creating a requirement link, the same mapping is used when you create a defect link between the same two endpoints.

The following chart describes how Synchronizer recognizes mapped users, using manual or automatic mapping methods.

Automatic user mapping

ALM users defined with an email address that is identical to the one used to log in to Agile Manager are automatically mapped for all user list fields.

If a user has multiple email addresses defined in ALM, only the first email address is synchronized with Agile Manager.

When the Agile Manager user list does not contain a user that matches the ALM user, then:

  1. If you defined a Default user for the Agile Manager endpoint, this user is mapped to the ALM user.
  2. If no default is defined, and the ALM user has a valid email address, Synchronizer uses this email address in the relevant Agile Manager user field. The user is not added to the Agile Manager user list.
  3. If no default is defined, and the ALM user does not have a valid email address, then the automatic mapping fails. Manually map this ALM user to an existing Agile Manager user.

Manual user mapping

Map ALM and Agile Manager users manually if the email addresses are not identical, or if the ALM user is not defined with an email address.