Yes, Ketryx can convert existing Jira native links to Ketryx custom relational fields!

This can be done in 2 different ways. The first one is to read in the Jira native links into Ketryx and map them to relations. The second one is by doing a migration of the Jira native links to the Ketryx relational fields.

1. If you wish to keep your Jira native links, Ketryx can recognize these links if they match the Ketryx relation names, which can also be configured here. This is done through the Organization-level Advanced Configuration "Relation names". An example of a json block that converts Jira links to Ketryx relations can be found below. In this case a Jira link with description "is child of parent" gets mapped to the "HAS_PARENT" Ketryx relation, a Jira link with description "relates to" or "is related to" gets mapped to the "RELATES_TO" Ketryx relation.

{
"HAS_PARENT": [
"is child of parent"
],
"RELATES_TO": [
"relates to",
"is related to"
]
}

2. This can be done utilizing an internal conversion tool that will allow the user to group Jira native links based on their two issue types and link type and convert those links to Ketryx relational fields.

Note: A Jira limitation put on the population of a custom select field that Ketryx creates is the fact that a select field has a limit of 10,000 options. The implication of that is that when you have over 10,000 items, the relational field will no longer populate new items in that select field. At this point, you can utilize either the traceability widget or mapping of Jira native links to convert to Ketryx relations. This Article goes over this configuration.