Skip to main content
Version: Early Access

Relationships

Relationships refer to the connections or associations between different data entities in one application and their corresponding entities in another. These relationships are essential for ensuring that data is accurately synchronized and consistent across both systems.

Syncing the Parent-Child Relationships​

Click the Relationships toggle button to define the parent-child relationship between the mapping you create or edit, and the other mapping.

Parent-Child relationship for defect is supported only with Portfolio Items and not with other asset types.

For example, if you have a mapping created to sync Digital.ai Agility and Jira Epics (parent), you can enable Relationships and select another mapping (from the drop-down list) created to sync Digital.ai Agility and Jira Stories, for example, as a child. Once done, any Story you create or update—as a child of an Epic—would be synced exactly with the same relationship on the other tool.

Setting up Relationships is not possible with ServiceNow.

Reltionships

Syncing the Linked Issues field in Jira to the Portfolio Item Field in Agility​

The Relationships function has been extended to sync the Linked Issues field in Jira to the Portfolio Item field in Agility. The use case is to sync the Jira Linked Issued field of type "Parent of" with the Portfolio Item field in Agility.

Relationship Fields

Regardless of the kind of link you create between two Jira issues using the Linked Issues field, the linked issue in Jira becomes the Portfolio Item in Agility. In other words, Agility Connect considers other types of links between Jira issues such as "clones", "is cloned by", "created by", etc., (including other custom link types) as "Parent of" link.

Parent-Child-relationship

 Here's an example where the Jira issue DP4-19 has been configured as the parent of DP4-20.

 

 Once the Jira issues DP4-19 and DP4-20 are synced with Agility as E-01782 and E-01754 respectively, you can see that the Agility Epic E-01782 shows up as the Portfolio Item in E-01754 as illustrated in the following image.

JIRA-Agility-Sync

Agility Sync now supports parent and child relationship from Related Links section and at Field level as well. The configuration changes required for this relationship are done in the Relationship section.

If you have a reference field in your asset and you plan to add a child to that asset, then all the fields associated with the reference asset are included as options in the System Relationship Mapping Details section.

Relationship-ref-mapping

Support for Sync Selected Event for Every Field​

Agility Sync now has the option to Sync Selected Event Typefor all the fields. You can click the Settings icon next to the Create field and select either CREATE or UPDATE event type as per your requirement.

If you select CREATE event type the value in the field is synced only for Create event type the Update actions are skipped. Similarly, if you select UPDATE event type the value in the field is synced for Update event type the Create actions are skipped.

If you do not select either of these options Agility picks up all the actions and syncs the field values.

ServiceNow Event Type

Conflict Resolution​

For Conflict Resolution, the precedence is given to mapping level, even if field level mapping is selected. The field level mappings are ignored if Conflict Resolution is enabled at mapping level.