#USER MAPPED MANUAL#

Map ALM or Jira and ALM Octane users manually if the email addresses are not identical, or if the ALM or Jira user is not defined with an email address.Ĭaution: In ALM, user fields can be set to Verify value. When you are done, re-run synchronization. For details on adding or activating users in ALM Octane, see Assign roles and permissions. You can manually map this ALM or Jira user to an existing ALM Octane user, or create a new user (either active or inactive) with the email address defined in ALM or Jira. If no default is defined, synchronization fails. If you defined a Default user for the ALM Octane endpoint, this user is mapped to the ALM or Jira user. When the ALM Octane user list does not contain a user that matches the ALM or Jira user, then: If a user has multiple email addresses defined in ALM or Jira, only the first email address is synchronized with ALM Octane.

#USER MAPPED MANUAL#

The following chart describes how ALM Octane Synchronizer recognizes mapped users, using manual or automatic mapping methods.ĪLM or Jira users defined with an email address that is identical to the one used to log in to ALM Octane are automatically mapped for all user list fields. This means that if you mapped the users between an ALM Octane workspace and an ALM or Jira project when creating a requirement link, the same mapping is used when you create a defect link between the same two endpoints. Users in these lists are mapped once for each pair of endpoints. ALM Octane and ALM or Jira maintain separate lists of user list fields, such as for the Owner field.

User mapped