TFS4JIRA Cloud Native | Creating links to opposite environment's item
TFS4JIRA Cloud Native supports a functionality where links to opposite environments are created in the item’s custom fields. This article provides all the information concerning this functionality.
Azure DevOps field example:
Jira field example:
FACTS
Functionality only works on item creation, item editions will not populate the link field.
The link in ADO is held as plain text, it needs to be copied and run in the browser
The link in JIRA is an active link (clickable)
By default, the functionality only creates links in the designated environment with information on the source item, for example, TFS4JIRA migrated ADO to JIRA. A Jira issue is created and that issue will hold a link to the ADO work item, however, the ADO work item will not hold a link to the Jira issue.
If bi-directional link creation is needed, please notify Appfire support about that need, providing your Tenant ID.
how to obtain Tenant ID - TFS4JIRA Cloud Native | How to obtain Tenant ID
CONFIGURATION
Please create a custom field in Jira instance
set any name
type: Text Field (single line)
make sure this field is available on all issue types used in migration/sync
Please create a custom field in ADO environment
set any name
type: Text (single line)
make sure this field is available on all work items types used in migration/sync
In TFS4JIRA Cloud Native please go to MAPPINGS->FIELDS and setup
JIRA | Azure DevOps |
---|---|
Issue Key | Created custom field |
Created custom field | "ID (System.Id)" |
Example:
Â