Link properties include all information about the link. Some main properties are displayed for all links in a sortable grid, and additional properties are displayed for a specific link in a series of tabs.
Open a link from the main grid or the navigation tree on the left to view or edit link properties. Tabs differ for each link, depending on whether you are synchronizing releases, defects, or user stories in the selected link.
Click Refresh or select Link > Refresh to refresh the data displayed in the grid or the link details tabs.
![]() |
Select the type of team you are configuring to filter the tasks below. |
The following information is customized according to your selections. Check that your selections are correct.
If any selections are not correct, click Change.
Open the link and click Edit .
You can have unsaved changes in multiple links. Unsaved changes are indicated by a red asterisk next to the link's icon in the navigation tree.
Caution: Editing a link disables the link, and changes the link's status to Unvalidated. You must save your changes and enable the link again before you can run synchronization tasks on it, as described in Enable or disable a link.
Before editing a link, verify that you do not need to run synchronization tasks.
Click the Filters tab.
In edit mode, click Refresh Filter Lists to display the current list of filters for each endpoint.
For each endpoint, select one of the following options:
No Filter | All records are considered for synchronization. |
Use filters (for creation events) |
Only enabled if there are filters in the endpoint available for the user.
|
Click the Subtype Mapping tab.
Tip:
If you do not see the Subtype Mapping tab, verify that you are editing a requirement link. To edit defects, see View or update synchronization rules for defects or View or update mapped fields for defects or releases.
Synchronizing requirements involves many details. Read through Guidelines for synchronizing requirements and user stories before you begin.
In edit mode:
Select a type for each endpoint, and click Add Mapping. The mapped pair is added to the Mapped Subtypes list.
For example, select the Feature type in the HP-ALM list, and then the Feature type in the HP-Agile-Manager list to map these requirements as a pair.
In the Mapped Subtypes list or the navigation tree, select a pair, and click Configure to define field mapping and synchronization rules for that pair.
Caution: Deleting a requirement type mapping deletes all identity mapping data for the selected pair. For additional important information, see Delete synchronization links.
In the Rules tab, configure synchronization rules for the selected mapped pair of requirement types. You can verify which pair you are configuring by checking the highlighted pair in the navigation tree. Define the following options:
Master and Creation |
Define which endpoint you want to define as the Master endpoint. For example, if you plan to manage requirements as user stories in Agile Manager, select Master in the HP-Agile-Manager column. Rules for newly created records are automatically set. |
Update |
For updated records, define rules in the non-master endpoint only. |
Deletion |
For deleted records, define rules in both endpoints. Tip: For the non-master endpoint, ensure that synchronized records are not accidentally deleted by selecting Recreate based on its corresponding record in the other endpoint. |
In the Field Mapping tab, map fields for the selected mapped pair of requirement types. You can verify which pair you are configuring by checking the highlighted pair in the navigation tree. For details, see Map endpoint fields and Modify .csv map files in a text editor.
Configuration rules direct Synchronizer how to handle the creation, update, and deletion of defects in each endpoint.
Click the Rules tab.
In edit mode, set rules for each endpoint, for the following scenarios:
Configuration rules direct Synchronizer how to handle the creation, update, and deletion of releases or sprints in each endpoint.
Click the Rules tab.
In edit mode, set rules as follows:
Select Map pairs of new releases or sprints found with identical names if you want to automatically map new releases or sprints found in both endpoints with identical names.
Note: If this field is cleared and Synchronizer encounters a pair of identically named releases or sprints, the pair of releases or sprints is not synchronized, and an error is generated in the run report.
Set rules for each endpoint, for the following scenarios:
Click the Field Mapping tab.
Tip: If you do not see the Field Mapping tab, verify that you are editing a defect link. To map fields for requirements, see View or update mapped data and rules for requirements.
You must define field mappings for each link. For details, see Map endpoint fields and Modify .csv map files in a text editor.