Map user list fields

ALM Octane and ALM or JIRA maintain separate lists of user list fields, such as for the Owner field.

Users in these lists are mapped once for each pair of endpoints. 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.

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

Automatic user mapping

ALM 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.

If a user has multiple email addresses defined in ALM or JIRA, only the first email address is synchronized with ALM Octane.

When the ALM Octane user list does not contain a user that matches the ALM or JIRA user, then:

  1. If you defined a Default user for the ALM Octane endpoint, this user is mapped to the ALM or JIRA user.

  2. If no default is defined, synchronization fails. 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. For details on adding or activating users in ALM Octane, see Assign roles and permissions.

    When you are done, re-run synchronization.

Manual user mapping

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.

Import a user mapping file

You can prepare a .csv file containing a list of user mapping pairs, and then import it to ALM Octane.

  1. Prepare a .csv file with a list of user mapping pairss, using the following format:

    <ALM/JIRA user name>,<direction>,<ALM Octane user address>

    Use <, >, or <> to specify the direction of the mapping.

  2. (Optional) Define default users for when there is no matching user in the destination endpoint.

    Example: For example:

    Default,>,OctaneUser1@acme.com
    ALMUser1,<,Default
    ALMUser2,<>,OctaneUser2@acme.com

    This means that if you synchronize a defect in JIRA with an author named John Doe and there is no mapping of this user in ALM Octane, the defect's author in ALM Octane will be OctaneUser1@acme.com.

  3. Select More Actions > Import User Mapping File.

  4. Browse to the file and click Import.

    A message appears showing the number of users imported from the .csv file.

If users are not mapped explicitly in the file, the Synchronizer will try to map them automatically using e-mail address.

How mapping conflicts are resolved

Imported mappings do not delete existing mappings. In case of conflict, the following rules apply:

Rule For example:
A bi-directional mapping (<>) overwrites a uni-directional mapping.

If the original mapping contains bob < bob@octane and the file contains bob <> bob@octane, the original mapping is overwritten, resulting in bob <> bob@octane.

If the original mapping contains bob <> bob@octane and the file contains bob < bob@octane, the original mapping overrules the file mapping.

Uni-directional mappings are merged. If the original mapping contains bob < bob@octane and the file contains bob > bob@octane, the result is bob <> bob@octane.

The mapping in the import file overwrites the original mapping if the original mapping is uni-directional, or if both mappings are bi-directional.

If the original mapping contains bob <> bob@octane and the file contains bob <> john@octane, the result is bob <> john@octane.