Note: This topic is relevant for ALM Synchronizer for Agile Manager only. For details about the NextGen Synchronizer see NextGen Synchronizer, or search using the NextGen Synchronizer filter.
If you are still using ALM Synchronizer, we recommend migrating to the more robust NextGen Synchronizer embedded in Agile Manager's configuration area.
Each synchronization link defines the following:
- The entities synchronized (defects, user stories/requirements, or releases). Each link can synchronize only one type of entity.
- The directions in which the endpoints are updated (ALM > Agile Manager, Agile Manager > ALM, or both).
- The filters used to find records with new data.
Multiple links
Each link synchronizes a specific entity type between a single ALM project and a single Agile Manager workspace. Create separate links to synchronize defects, requirements, and releases between the same two endpoints.
You can create multiple links between a single Agile Manager workspace and multiple ALM projects. In such a case, use Agile Manager favorites to separate the synchronized data inside the workspace.
To prevent data leaks between workspaces, Synchronizer does not support multiple links between a single ALM project and multiple Agile Manager workspaces in the same site.
Link filters
Synchronizer looks for new records in ALM or Agile Manager based on the filter defined for the link task. If no filter is defined, all records are considered for synchronization.
Filters are based on ALM or Agile Manager favorites, and must be available in the endpoint to the user defined for the current link. You can select from a maximum of 50 filters for a specific endpoint.
Tip: When first setting up Synchronizer, synchronize a filter that contains only one defect or requirement to verify that the synchronization works as you expect. Enlarge the filter slowly, verifying that the synchronization continues to update information as you expect, until you've covered the variety of scenarios in which you need to synchronize data.
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. Be sure that you want to synchronize data in a specific record or type of record before including it in your filter.
| In the Agile Manager endpoint... | In the ALM endpoint... |
|---|---|
|
Filters must be defined as favorites in the Product Backlog > Backlog page. |
Filters must be defined in the ALM Requirements Tree view, and not the Requirements Grid view. |
For more details, see View or update link filters (defects or requirements).
Link mapping data
Each synchronization link includes definitions for field mapping, which specifies the pairs of mapped fields and the direction in which each pair of fields is mapped. You can also map specific values for a field in one endpoint to specific values of a field in the other endpoint.
Example:
You might map a field named Priority in one endpoint to a field named Criticality in the other endpoint. You might also have Priority values of 1, 2, and 3 in one endpoint mapped to Criticality values of Low, Medium, and High in the other endpoint.
For task details, see Map endpoint fields.
