Skip to end of banner
Go to start of banner

TFS4JIRA Cloud Native | Creating links to opposite environment's item

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

TFS4JIRA Cloud Native supports a functionality where links to opposite environments are created in the item’s custom fields. This article holds all the information concerning this functionality.

Azure DevOps field example:

Jira field example:

FACTS

  1. Functionality only works on item creation, item editions will not populate the link field.

  2. The link in Jira is held as plain text, it needs to be copied and run in the browser

  3. The link in Jira is an active link (clickable)

  4. 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.

  5. If bi-directional link creation is needed, please notify Appfire support about that need, providing your Tenant ID.

    1. how to obtain Tenant ID - https://spartez-software.atlassian.net/servicedesk/customer/kb/view/2558001157

CONFIGURATION

  1. Please create a custom field in Jira instance

    1. set any name

    2. type: Text Field (single line)

    3. make sure this field is available on all issue types used in migration/sync

  2. Please create a custom field in ADO environment

    1. set any name

    2. type: Text (single line)

    3. make sure this field is available on all work items types used in migration/sync

  3. 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:

  • No labels