There are two main reasons for this:
- Native links can go from any issue to any other issue, so you can't restrict the target of a particular relation. For instance, a has parent relation might point to any other item, while the Parent requirements fields can be restricted to only contain other Requirements as options.
- You can edit native links even when a ticket is otherwise read-only, i.e. even when the issue is already Resolved or Closed.
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.
That being said, Ketryx also recognizes native Jira links as long as they match the Ketryx relation names. These names can also be configured using the advanced setting Relation names. If you prefer to work with Jira links, you can use these, and potentially remove certain relation fields using the advanced setting Item fields.
Comments
0 comments
Article is closed for comments.