Why does Ketryx introduce custom relation fields rather than using Jira's native links?

Lee Chickering
Lee Chickering
  • Updated
There are two main reasons for this:
  1. 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.
  2. You can edit native links even when a ticket is otherwise read-only, i.e. even when the issue is already Resolved or Closed.
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.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request



Article is closed for comments.