Once a record in one endpoint is mapped to a record in the other endpoint, it is always synchronized if there is new data, regardless of whether the record still matches the link's filter. Therefore, before you start synchronizing, it is highly recommended that you read the following guidelines for specific types of synchronizations.
For details of how attachments are synchronized, see Mapping attachments.
Mapping field values when the number of values differ in each endpoint
If you have a different number of values for the field in each endpoint, make sure each value is mapped to a value in the other endpoint.
New field values created during synchronization (Synchronize back on create)
ALM Octane Synchronizer sends any new field values created in a destination endpoint (during synchronization) back to the source endpoint, if they are mapped.
Mapping value list fields
You can synchronize value list fields between ALM or Jira and ALM Octane. This includes value list fields of type release, team, user, and string (for example, if a defect impacts a number of releases, or a number of teams).
You can also map list fields to a string, for example to save them for reference. For releases, teams, and users the direction of mapping is one direction only, from list -> string. In the case of a single value list of strings, it can be synchronized in both directions.
Automatic field value mapping
If you have identical list values in both ALM or Jira, and in ALM Octane, they are automatically mapped when you run an integrity check. For example, if you have a Priority list field with the values <Low;Medium;High> in Jira, and you have the same values defined in ALM Octane, you do not need to map these values to each other. During the integrity check they are automatically mapped, and you only need to map the values that are unique to one of the endpoints. If you do not map a value that is unique on one endpoint, you will receive an error when you run synchronization.
Values are automatically mapped by name in the case of simple lists (strings, numbers), releases, labels and teams. For users, mapping is done according to email address.
Note: It is important to distinguish between Synchronizer endpoint links (such as those between ALM and ALM Octane) and entity links between entities, such as defects
Links between entities are not synchronized.
If you map ALM Target Cycle or Detected in Cycle fields, you must also map the corresponding release fields.
Release and cycle or sprint names must be identical in both endpoints. These names are case-sensitive.
Release names must be unique in both endpoints.
Requirements must have a single target release in ALM. Synchronizing requirements from ALM with multiple target releases will fail.
Tip: If you cannot modify these release names but you want to map these fields:
Map specific field values to define the full path of the release. For example, you can map each value of the Target Release field to a value in a corresponding field in the other endpoint.
Define the full path of the ALM release in the format
\<Release_Folder_Name>\<Release_Name>. For example,
You do not need to include the root Releases folder in the path.
For details about mapping specific field values, see View other field properties.