nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problems with double 'relates to' issue link when addressing through linkedIssues("relates to")

Nikolai Klyukach

Linking issues through a link type "relates to" is ambiguous in Jira. Since there are two "relates to"'s, it is not possible to address related issues using Nunjacks code:

{% set links = issue | linkedIssues("relates to") %}

Two "relates to"'s are visible in the field "Link Type" in creating or editing Post Functions in Workflow administration.

Is it possible to merge these links into one or at least rename one of the "relates to", so that the above code addresses the correct issues?

Comments

Nic Brough -Adaptavist-

I suspect there is only one link here. Links in Jira are vectors, so you can form a sentence like "issue X depends on issue Y" and "Issue Y is depended on by issue X" - that is the same link, but directional.

Off the shelf, Jira ships with one link type which has the same label on both directions, so "X relates to Y" comes out as "Y relates to X" when looked at from the other end.

There's no "merge" you can do here, the two "relates to" are already the same link type.

But you can put different labels on them, or even remove the link type. Even something as simple as extra spaces or different capitalisation should allow your Nunjacks to uniquely identify one.