This topic is relevant for NextGen Synchronizer only, embedded in Agile Manager's configuration area. For details about the ALM Synchronizer, see for .
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 further recommendations before synchronizing, see Adapt the data in your endpoints.
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, select uni-directional mapping for the specific value mapping. Only one value can be synchronized back to the original endpoint, and if this field has a bi-directional mapping, Synchronizer may select the incorrect value in the original endpoint.
In uni-directional mapping, occurrences of the value in the source endpoint are mapped to the value in the destination endpoint. Occurrences of the value in the destination endpoint are not mapped to the value in the source endpoint.
Example: Mapping defect statuses.
New field values created during synchronization
NextGen Synchronizer always sends back any new field values created in a destination endpoint (during synchronization) back to the source endpoint. This is not configurable.
If you map a string field that has a maximum length in the destination endpoint, and a synchronized value exceeds this maximum, the string value will be truncated as necessary in the source endpoint during synchronization.
If you map ALM Target Cycle or Detected in Cycle fields, you must also map the corresponding release fields.
Additionally:
Tip: If you cannot modify these release names but you want to map these fields:
For details about mapping specific field values, see View other field properties.
Agile Manager supports both workspace teams, which are available for all releases in a workspace, as well as feature teams, which are available for a specific release only. Although it is not recommended to have a workspace team and feature team with the same name in the same release to prevent confusion and errors, separate teams of different types with the same name are supported.
Such teams are synchronized as follows:
Agile Manager > ALM | A workspace team or a feature team defined for a record are synchronized to the same ALM team value. |
ALM > Agile Manager |
Synchronizer first checks for a release team with the name in the record's defined release. If a feature team is found with the configured name, the record is synchronized with the feature team. If there is no release defined for the record, or if there is no feature team found in the defined release with the configured name, Synchronizer searches for a workspace team with that name. If the workspace team is found, the record is synchronized with that team value. If no team is found with the configured name, an error occurs. If there is no team defined for the record, no team value is assigned during synchronization. |
Files attached to backlog items in either ALM or Agile Manager are not currently synchronized to the other endpoint.
This means that files that are attached to a record in one endpoint are not automatically accessible (after synchronization) from the other endpoint.
The attached files in the source endpoint are not affected.
NextGen Synchronizer does not currently support synchronizing links between entities, such as links between defects and requirements. This means that records that are linked in one endpoint are not automatically linked (after synchronization) in the other endpoint.
The links between records in the source endpoint are not affected.
Backlog Item custom fields do not currently support synchronization. If you synchronize data with ALM, Backlog Item custom fields created in Agile Manager will not be synchronized.
For more details, see Créer des champs personnalisés.