Understanding inward and outward link in terms of parent and child relationship,

Hi folks,


I need some clarification for the linked issues,As I am new to jira,

I got the link from forum as https://confluence.atlassian.com/display/JIRA051/Outward+Link+Description+and+Inward+Link+Description ,


But need some clarity on this, Lets say there is one issue as issue-1 and there is a link to it as blocks issue-2 , so in this scenario which issue will be child issue and which issue will be parent,

So how do we interpret it

either : issue-1 blocks issue-2

OR : issue-2 blocks issue-1


Please explain what will be parent issue in this case and which will be child,


Thanks in advance,

1 answer

1 accepted

1 vote

There is no parent/child relationship in links.  What there is is a directional piece of information.

If you go and look at the link definitions you will find that each link type has "inward" and "outward" definitions, and you really need to be very clear when you define these, as in most cases, the language tells you the direction.

It helps to think of it in a sentence, much as you have typed in your question - "issue 1 blocks issue 2"

For "blocked", you want some language like

Inward: is blocked by

Outward: blocks

This way, you can accurately describe the direction of the link from either side, because it will say "Issue 1 is blocked by issue 2" or "Issue 2 blocks issue 1" - either way, it is clear which one is the blocker, and what it is blocking

If your JIRA has been amended to remove that directional language, I'd strongly recommend putting it back!  (It is directional by default)

One exception is in the defaults - when you want a non-directional relationship such as the rather vague "relates to".  Then you use the same phrase for both directions

Nice Explanation Nic, thanks --cheers,

If A 'Blocks' B (outward), does B also 'Blocked By' A (inward).

Or: Is issue linking symmetrical?

Issue linking is not symmetrical, it's directional.  A blocks B, therefore B is blocked by A

You can use the names differently if you want to.  A never ending blocked loop could be done by saying "blocks" on both inward and outward descriptions (A blocks B, therefore B blocks A), but there's not many uses for same-named directions beyond the very generic idea of "related to"

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,327 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot