Version: Early Access

Known Issues and Limitations

ServiceNow

Agility Connect supports only the Requirement and Defect modules of Micro Focus ALM QC.

When a mapping is created, webhooks are automatically created in both the source and target tools that are being integrated. However, you must configure the webhooks manually in the case of TeamForge. You must configure webhooks in both Digital.ai Agility and TeamForge, for example, after creating a mapping to integrate Digital.ai Agility and TeamForge.
Sync Reference is enabled for Agility—TeamForge integration. However, you must create the ID and URL TeamForge custom fields and map them with Agility's ID and URL fields (when you create an Agility—TeamForge mapping) to have the backlinks synced between TeamForge and Agility.
Auto-mapping of fields is not defined for TeamForge asset types and so you cannot automatically map TeamForge fields with other tools.

Auto-mapping of fields is not defined for Microsoft Azure DevOps Service asset types and so you cannot automatically map Microsoft Azure DevOps Service fields with other tools.
When you map fields from hosted Jira and Microsoft Azure DevOps Service assets and when sync happens for a create or update event—all but the user type fields are synced successfully. The user type fields are ignored.
Parent-Child relationship for defect is supported only with Portfolio Items and not with other asset types.

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

A validation message appears when you map text and single-select fields without selecting a default value.
The field mapping page goes blank when you map text and single-select fields bi-directionally and add a default value to it.