Hey folks! I’m trying to wrap my head around Jira issue links. I get how cloning and duplicates work, but I’m confused about the ‘related’ and ‘relative’ links.
When you link issues as related, one side shows ‘This issue is related to…’ while the other says ‘This issue is a relative of…’. It’s a bit weird seeing an issue that’s ‘a relative of’ some tickets and ‘related to’ others.
How do you guys use these link types? Is there a difference between them, or are they just two sides of the same coin? I’m curious how other dev teams handle this.
It’d be great to hear your thoughts on this. Thanks!
In my experience, the ‘related’ and ‘relative’ issue links in Jira are indeed two sides of the same relationship. The terminology difference is merely a quirk of Jira’s interface design. When managing projects, I focus on the practical aspect: these links indicate a connection between issues without implying a specific hierarchy or dependency. For our team, we use these links to group thematically similar tasks or to connect issues that might impact each other indirectly. The key is consistency in how your team applies these links, rather than getting caught up in the semantic nuances of Jira’s labeling.
As someone who’s been in the trenches with Jira for years, I can tell you that the ‘related’ and ‘relative’ issue links are essentially interchangeable. It’s just Jira’s way of showing the same relationship from both sides. In our team, we use these links liberally to create a web of connections between issues that have some sort of impact on each other, but don’t fit into the more structured parent-child or blocks-blocked by relationships.
We’ve found it particularly useful for connecting issues across different projects or epics that might not otherwise be obviously linked. For example, a UI change in one project might affect the user flow in another. By linking them as ‘related’, we ensure that developers working on either side are aware of the potential ripple effects.
Don’t get too hung up on the terminology. The important thing is to establish a consistent practice within your team for when and how to use these links. It’s all about improving visibility and communication, not adhering to strict definitions of ‘related’ versus ‘relative’.
hey, im using jira for a while and its kinda trippy. i reckon related and relative are functionally same. its more a display issue than a real diff. im not overthinking it.