Different linked issues in JIRA and its meaning

[Sumeet]

During creating an issue, I get an attribute: Linked Issues <Value>.

Please help me in understanding the different values available. For eg. Linked Issues 'Implements' etc.

[Grigory Salnikov]

Hi,

With the help of linked issues you can bind together issues in your project. Let's take a look at the example.

There's an issue ADM-100 "Setup a CentOS server" assigned to a system administrator. We want to install Confluence on that server. So when I create the next issue ADM-101 "Install Confluence" I use Linked Issue functionality this way:

ADM-101 is blocked by ADM-100

ADM-100 blocks ADM-101

Meaning that I cannot install Confluence without a Linux server already set up.

You can create your own links to use in your project.

Hope this helps :)

[aerhoads]

Two items you may be able to assist with.  

1. When we have a task (DWO-1) that is blocked by another task (DWO-2), we link them together.  No problem with any of that.  But, when we look at DWO-1, we see that it is blocked by DWO-2, which is correct.  However, even though DWO-2 has not reached the end of it's workflow, it has a strikethrough when it is displayed as the blocker for DWO-1.  Is it because the workflow status sits in the last column of the COLUMNS in the Board Configuration?

2.  We are trying to build a quickfilter on our boards that displays all tasks that are NOT BLOCKED.  Here is the JQL we have come up with that works ALMOST perfectly:

issueFunction not in hasLinks("depends on") OR (issueFunction in hasLinks("depends on") AND issueFunction in linkedIssuesOf("Status = Done"))

But if a task has more than one blocker, and one of them is done and the others are not, this query shows it as NOT BLOCKED since it has one blocker in DONE Status.

Any ideas how to rewrite the query so it will recognize that even though one blocker has been completed, the task is still blocked???

[Kian Stack Mumo Systems]

Hey Sumeet, 

Issue links in JIRA are just a way to define how issues are related to each other. For example, one issue within JIRA, ET-2, may have been created by cloning another issue, ET-1. In that case, we would say ET-2 "clones" ET-1 and ET-1 is "clone by" ET-2. This is just allowing us to see how issues correspond with other issues in the system. 

Another example might be if one issue requires another to be completed before the first issue can be worked on. We might say that because issue ET-4 requires ET-3 to be finished, ET-4 is "Blocked" by ET-3. We would also want to make sure to note that ET-3 "Blocks" ET-4. 

Each link defines a different relationship with other tickets within the system. More information can be found here.