Example of mapping field values

Note: This topic is relevant for NextGen Synchronizer only. For details about the ALM Synchronizer, see ALM Synchronizer for Agile Manager or search using the ALM Synchronizer filter.

Synchronizer enables you to map specific field values in one endpoint to specific values for the corresponding field in the other endpoint. A good example of when you might need to do this is when mapping defect statuses.

Agile Manager and ALM each have different lists of defect statuses, and even different numbers of available statuses.

  • The Agile Manager Defect Status field has the following values: New, Open, Fixed, Propose Close, Closed, Deferred, Duplicate, Rejected
  • By default, the ALM Status field has the following values for defects: New, Open, Fixed, Closed, Rejected, Reopen

Because these are standard fields, Synchronizer provides a default mapping for these values, shown in the table below.

You can modify the mapping as needed for your link.

Tip: Make unidirectional mappings before you make the bidirectional ones.

For example, if one endpoint has Rejected and Duplicate and the other endpoint has only Rejected, map Duplicate to Rejected unidirectionally before you map Rejected to Rejected bidirectionally.

Dominant Endpoint: Agile Manager
Agile Manager Direction ALM
New Bidirectional New


Fixed Bidirectional Fixed
Propose Close Bidirectional Rejected
Closed Bidirectional Closed




Rejected Bidirectional Rejected
Open Bidirectional Open

In this example, you can see that the ALM's Reopen value will be synchronized to Agile Manager as Open, but no Agile Manager value is synchronized to ALM as Reopen. Open in Agile Manager is synchronized to ALM as Open.

Note: This means that if the Status field itself is mapped to synchronize bidirectionally, a defect's status in ALM may change from Reopen to Open as a result of the defect being synchronized back and forth between ALM and Agile Manager.