When creating an issue link type, I understand that the inward and outward descriptions clarify the relationship between the issue; i.e. A blocks B, and B is blocked by A.
What I don't understand is if it matters which description is "inward" and which is "outward"?
Is there some implied meaning behind those terms? Is JIRA core using the "inward description" for some purpose, and/or the "outward description" for some other purpose
When you make a link between issues, one of the issues has the outward connection and the other one has the inward connection. You have these two connections because if you have a link called Blocks, then one issue is blocking the other issue and the other issue is blocked by first issue. That is why you need two different descriptions.
I suspect that the inward and outward thing is probably partly inherited from the code and how the language is used in there. Sadly, it's still quite fuzzy on what the exact difference is.
Links are directional, and the inward/outward thing is supposed to tell us which direction you are looking at. For example, if you have a link of "Block", you are using it to say "Issue A is blocked by B". That description is only half the story, because you can also say "Issue B is blocking A". So it distinguishes between the two points of view.
But it doesn't really tell us which is which, as you could swap the descriptions of those without changing the inward/outward.
So, the answer is only partial. The inward/outward is about the directionality of the link, but I am not sure which way round it is.
The Inward/Outward refers to the directionality of the relationship as it is stored in the database. The table that stores issue links (issuelink) has a source issue id and a destination issue id. The outward relationship refers to the relation from source to destination, and the inward relationship refers to the relation from destination to source.
The outward relationship tends to be the relationship that is the causal direction, meaning the source issue is taking action on the destination issue.
i.e. the source issue can block, clone, duplicate, relate, resolve etc.
The inward relationship tends to describe the issue that was acted upon.
i.e. the destination issue was blocked by, cloned by, duplicated by, related to, and resolved by etc.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events