It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

jira query: issues with linked issues

SallyD May 05, 2013

I need to find all of the issues in my project that have links to other issues, which might not be in the same project. I can't figure out the field name for the "have links to" part. Can anyone help me?

22 answers

2 accepted

26 votes
Answer accepted
Andrew Heinzer Atlassian Team Apr 17, 2019

Hi everyone,

This is a rather old post now (6 years old), but I wanted to share an update in regards to this functionality in Jira.    Starting with Jira Server 8.0.0, Jira now has the native functionality to be able to search in JQL by link types.  Please see Advanced Searching: Field reference: Issue link type.

In Jira 8 and higher, you can search JQL with something such as as

Project = XYZ and issueLinkType in (blocks, causes)

This would return all the issues in project XYZ that have at least one issue link of either blocks or causes type that your account has permissions to see.  You can use multiple link types in the search here, if you included all the link types in your search you can then find all those issues that have links of any type.

If you're not on Jira 8 or higher, then Vidic's accepted answer of using a plugin would also be able to provide a solution here.  I hope this helps.

Cheers,

Andy

Carina Verdugo Apr 17, 2019

Good to know! Thanks!

Like # people like this
Marie Kent Apr 17, 2019

This is great news, thanks Andrew! Any plans to include the link type as a displayed field on filter results/dashboards?

Like # people like this
Vikiy Myers Apr 17, 2019

So, when does Cloud get this functionality please? We need it too!

Like # people like this
Becky Frost Apr 30, 2019

Ditto - this would be incredibly helpful for my team to see a report of changes that introduced bugs (and therefor have a "causes" issue link type).

Andrew Heinzer Atlassian Team Apr 30, 2019

@Vikiy Myers There is a corresponding Jira Cloud ticket for this in JRACLOUD-25640.  However I don't know if there is a set timetable on if or when it might be implemented in Jira Cloud.  I would watch that issue to see if this is coming to Cloud.  If it is, I would expect this to be updated to reflect that.

Natasha Denny Apr 30, 2019 • edited

Hi all - I'm attempting to run a query issuelinktype = blocker to show me all issues that have a blocked by or blocks link. When I run this query its not picking up all the links... anyone encountered this problem? 

It shows me everything up until end of February, but no later... 

Andrew Heinzer Atlassian Team May 01, 2019

@Natasha Denny That is not the correct usage here for searching of such issues with two different linktypes.  Instead try using

issuelinktype in (blocks, "is blocked by")

This will return all issues with either the blocks link type or the reciprocal linktype of 'is blocked by'.  You might have another custom linktype called 'blockers' that is not the same as blocks or 'is blocked by' linktypes.

Natasha Denny May 02, 2019

blocks or "is blocked by" are not available in the jql search for issuelinktype, only blocks, clones, duplicates

Andrew Heinzer Atlassian Team May 03, 2019

Hi Natasha,

These other link types are available by default.  However it is possible that in your site, these have been customized in some way to remove these 'is blocked by' reciprocal link names.  You can see more on how issue linking is configured in your site under Configuring issue linking.  Jira's JQL can only search on link types that exist in your Jira site.

Natasha Denny May 06, 2019

This is our issue link type set up: 

issue link type set up.PNG

Andrew Heinzer Atlassian Team May 07, 2019

Thanks Natasha,

I can see that you have many of the default link types, and a pair of custom ones.  You should be able to use the JQL syntax of

issueLinkType in (blocks, "is blocked by")

to find the issues that have either link type description (inward or outward description of links under the name blocker). Note that quotes are required for any inward/outward description that contain spaces.  Also you can't use the Name of the link to search (which is Blocker in your case), but instead you have to use the description of 'blocks' or 'is blocked by'.

If this didn't solve your problem, would you mind creating a separate thread in community for this problem, or creating a support request.  I fear that the replies of this might not be the best location to troubleshoot the specific problem you are seeing here.

Thanks

Andy

20 votes
Answer accepted
Vidic Florjan May 05, 2013
Vidic Florjan May 06, 2013

Related, unresolved issue in Atlassian Jira project: https://jira.atlassian.com/browse/JRA-25640

Like Najme Esmaili likes this
Jeroen Vandeweghe Mar 31, 2015

So there is no way to do this without plugins?

Like TeamCity Jetbrains likes this
lade Apr 29, 2015

Thanks for this, seems this functionality cant be met without plug-ins. Unfortunately, Installing plug-ins is currently not an option.

Ed Guy Aug 28, 2015

I also need to be able to do this without the Script Runner plug-in.

Joakim Borgström Jan 07, 2016

For me as well this is a must-have feature due to the abundance of simultaneous issues with and without blocks. Installing plug-ins is not an option.

Jack Murphy Apr 06, 2016

This functionality is essential for me too, and i also don't have the option of installing plugins.

Marian Reynov Apr 07, 2016

I could also use it. Why do I need a plugin for this - shouldn't issue link be searchable like all the other fields?

Richard Dodds Jul 08, 2016

Same frustration here; no ability to add plug-ins due to network systems folks not supporting it. Why isn't this capability part of the functions list?

Eerk Hofmeester Jul 12, 2016

I can see the column in a JQL result page, but can't filter for it in JQL...?

+1 here that this should be default functionality. +1 as well for the inability for mere mortals like me to be able/allowed to install plug-ins.

I'm managing five backlogs with a lot of related issues on other boards. I need to be able to see what issues can be closed when closing a related issue on another board. That's almost impossible without queries.

Colin Main Jul 12, 2016

I echo Eerk's comments almost word-for-word!

Even without the ability to drill down into link types, being able to query for any issue with a link would make a significant improvement to the current "nothing at all" capability.

prempal singh Aug 11, 2016

This is such an essential function and will help JIRA community at large, why no one from Atlassian is responding to his thread?

Marie Kent Sep 01, 2016

The other piece that should be added is a column to show the link type in the filter results.

Ed Vitalos Sep 15, 2016

Agree with all the comments. This needs to be a searchable field like all the others. No plug in should be needed.

AJ Sep 23, 2016

Agreed, This is basic functionality and should is in place.

I also agree with the comments.

Is there any JRA project issue to implement this? If not, how could we create it?

Thank you very much!

Philip Fung Oct 24, 2016

plugin is not needed.  Just go to Issue Navigator and put in the JQL query:

issue in linkedIssues(XXX-XX)

Like # people like this
Alan Williams Oct 26, 2016

Philip that works for a specific issue, but I think the idea is to for example query only issue types that have a specific issuetype linked to it.....ie only stories with bugs linked.

Like Kevin Mertens likes this
Jon Bertrand Dec 09, 2016

+1   - I'll go farther and push for email events here as well.  Your goal is to provide the tools that foster the development of strong processes.  The inability to send emails when dependencies change status cripples the strength of any processes that need to manage dependencies.  I know - not this issue.  Just venting a bit.

Like # people like this
Attila Strba Jan 18, 2017

I think this should be supported in a vanilla instalation. I guess this is  a standard use-case anybody can run into... so +1 from me ...

Like Jessy Mathault likes this
Mark Brogowicz Feb 20, 2017

Agreed.  Such a basic query.  Find me all issues that are currently blocked by another issue.  How is this not part of the base install?  

David Sumlin Apr 13, 2017

+1  Unfortunately, JIRA without plugins is akin to using an iPhone without any apps.

Fabian Schneiter Aug 08, 2017

I am completely stunned that this is not possible. D:

Katrin Kueper Sep 04, 2017

+1 I'm confused too that a product like Jira doesnot support something that I would consider basic functionality.

Amol Baviskar Apr 13, 2018

+ 1 - cannot believe JIRA does not support this 

Legna Garcia Apr 30, 2018

+1 Agree.

This is a critical management functionality that should be covered by Jira. I neither understand why, besides of the Jira licence we have to pay an extra plug-in. Also take on mind cloud version has limit amount of functionality than the server version.

The issue for cloud JRACLOUD-25640 , doesn't have any updates.

Like # people like this
Aurelie Navarro-Lee Jun 12, 2018 • edited

@Philip Fung- Thank you!  Your tip helped me (find filtered list of all jiras associated with 1 specific jira).

Like Brenda Higgs likes this
Bhogesh Nimmala Nov 11, 2018

cannot believe JIRA does not support this requirement, this is quite upset.

Like # people like this
Nima Zeighami I'm New Here Jan 25, 2019

I also feel VERY strongly that you should be able to search for tickets with Links.

Current Use Case:

1. We want to upgrade to Next-Gen Jira Project

2. Upgrading to a Next-Gen Project will break all Links between tickets

3. There's no way to search for all tickets with Links to take notes and rebuild the links later

Something that should take 20 minutes or less will now take multiple hours of work.  Atlassian needs to figure this out, there's no way this is a large engineering lift in comparison to the other things their working on, and the utility is HUGE.

Like Kelly Buchanan likes this
13 votes
Somya Upadhyay Jun 22, 2017 • edited

issueFunction in linkedIssuesOf("issuetype = Bug and project = projectName")

This helped me resolve the issue.

Charis Jun 22, 2017

How would you just get an additional parent of a particular ticket?

Your query would give all linked issue of a bug within a particular project. If we do that on our end, we end up too many tickets. 

Andrew Lang Aug 22, 2017

You can narrow it down to results where the outbound link type is <link type> by doing:

issueFunction in linkedIssuesOf("issuetype = Bug and project = projectName", <link type>)

So you might replace <link type> with

"is parent of"

You can narrow the returned results further by whatever criteria you want with:

issueFunction in linkedIssuesOf("issuetype = Bug and project = projectName", <link type>) AND <additional criteria>
Like # people like this
bthayer Oct 27, 2017

Is this the full JQL? I am not getting any relsults using it. And to clarify i am the site Admin so its not a permissions issue. All i am seeing is this:Capture.PNG

Like # people like this
Allison Carlson Apr 27, 2018

Somya Upadhyay - 

this worked!  issueFunction in linkedIssuesOf("issuetype = Bug and project = projectName") 

 

This allowed me to pull all Issues in a project with a linked issue 

Thank you!

Wilfried Möller Nov 05, 2018

Perfect, THX, that helped ;)

Looks like this is a ScriptRunner solution.

6 votes
Thu Trần Aroma May 03, 2017

I am on Jira 7.3 and here's the JQL statement I use to filter all the issues linked to some other issue(s):

 issue in linkedIssues("AAA-123")
Craig Cockburn Jul 27, 2017

That only provides the links to one issue which is of limited benefit

I'm looking for something like "show me all the bugs linked to all stories" so I can see what stories might be blocked

Using the blocking flag is really for an issue that isn't able to make progress at all and doesn't actually show me why it is blocked. The summary of the bug does.

Like # people like this
3 votes
lucy sogard Oct 11, 2017

I was successful using the following JQL:

issueFunction in linkedIssuesOf("filter = 'FILTER 1'")

My filter (which I'm calling 'FILTER 1' for anonymity) is fairly complex - I used JQL to narrow down ProjectIssuetype = Roadmap, and createdDate.

Using this filter combined with the JQL above pulled up all the child issues (Stories, Tasks, Bugs, Epics) of Roadmap issuetypes created after a certain date in my project.

I think this should work as long as your filter is shared with logged-in users/public. However I'm not sure if this JQL works without the plugin. I'm relatively new to JIRA and thus am not quite familiar with which functions are native to JIRA and which ones aren't. 

Liz Bedwell Nov 10, 2017

That is exactly what I am looking to do, but alas is does not work without the Plug In and the Plug In is not available on the Cloud versions.

I want to add another voice of annoyance to everyone else here, searching for issues that block the issues you are tracking and what type of link that may be (is dependant on, blocks, etc) is an essential feature. Even my old company that had an in house developed bug tracking software with an interface done in Adobe Air could bring up a search for all tickets that blocked or were dependant on other tickets. Shame Atlassian for not considering this (as it is stated in their Backlog that is no longer part of their roadmap: https://jira.atlassian.com/browse/JRACLOUD-22024)

2 votes
Hanna Blomqvist Jun 25, 2017

Is there a feature request ticket about this, does anyone know? Does Atlassian follow these discussions at all?

2 votes
Ray Maxwell Sep 01, 2017

This thread has been going for 5 years and Atlassians answer is use a plugin to resolve the issue.  

Then they anounce a new pricing structure.

I have a product manager that needs to track the dependancies and we have to jump through hoops to do this.

Been using JIRA for 11 years and this is a typical problem.  It takes them for ever to fix or improve small request like this because they use voting on everything. 

No answer but just adding to the Atlassian frustration.

2 votes
Stephen Burke Aug 22, 2018 • edited

I´ve tried most if not all of the work arounds ( not solutions) here above and have not found a satisfactory solution. It must be possible for Atlassian to provide a standard filter to show linked issues. Of course I can use excel but then again if I wished I could do everything in excel.

This function should really be out of the box. Come on Atlassian let´s see how customer friendly you are?

Steven Dillon Sep 27, 2018

I totally agree 

Filip Pokorny Sep 27, 2018

What's wrong with the solution offered by Darryl Duke 15h April 2017? Is there something wrong with the following?

issue in hasLink("Implements") 

Michael Sedovic Oct 23, 2018

@Filip Pokorny

I get the below error when I try Darryl's solution. 

Unable to find JQL function 'hasLink(blocks)'.

Filip Pokorny Oct 23, 2018

hasLinkBlocks.png

I just tried now and it works, 

JIRA v7.6.1 Server

Like TeamCity Jetbrains likes this
Christine Ritchie Oct 24, 2018

that's because your company has paid more for the plug in... it doesn't come free.

Filip Pokorny Oct 24, 2018

You're right. I checked just for the Scriptrunner which we don't have, but forgot that it might be part of the R4J requirements plugin. And it is. It makes all sense now.

1 vote
Darryl Duke Apr 15, 2017

To get issues with links, add this to your JQL:

issue in hasLinks()

(JIRA 7.2.4)

Ming Lam Apr 24, 2017

I cannot find this hasLinks() function in JIRA docuemntation or JIRA release notes: https://confluence.atlassian.com/jirasoftware/jira-software-7-2-x-release-notes-826896227.html

Like Kevin Mote likes this
Shanyn doCarmo May 03, 2017

@ming Lam this command is from the plug in... 
+1 on needing this to be standard functionality! I used this all the time at my last job and didnt even realize it was a plug-in until I left and tried to use it in another instance

Filip Pokorny Sep 18, 2018

You're the only one who suggested solution without any plugin needed. Thank you!

1 vote
Kate Asaff Sep 01, 2017

I found a way to do this  by exporting the total list of issues into Excel, then filtering from there based on the linked field.  It's not pretty, and it's a pain in the a$$, but it gets it done.  I agree this should be native functionality in Jira thought, would be so much easier!

1 vote
lucy sogard Oct 11, 2017 • edited

I was successful using the following JQL:

issueFunction in linkedIssuesOf("filter = 'FILTER 1'")

My filter (which I'm calling 'FILTER 1' for anonymity) is fairly complex - I used JQL to narrow down ProjectIssuetype = Roadmap, and createdDate.

Using this filter combined with the JQL above pulled up all the child issues (Stories, Tasks, Bugs, Epics) of Roadmap issuetypes created after a certain date in my project.

I think this should work as long as your filter is shared with logged-in users/public. However I'm not sure if this JQL works without the plugin. I'm relatively new to JIRA and thus am not quite familiar with which functions are native to JIRA and which ones aren't. 

Kevin Mote Nov 08, 2018

issueFunction requires ScriptRunner plugin

1 vote
Julien Fritsch Nov 16, 2017

Using the JQL "issue in hasLinks("")" works perfectly, but is there a way to get the one more step and to select the issues that have links .... that are resolved or not?

Thu Trần Aroma Feb 06, 2018

just add the criteria like this

issueFunction in hasLinks("relates to") and resolution is not EMPTY
1 vote
B Feb 13, 2018 • edited

You don't need a plugin to do this.  JQL alone can do it.

To find issues which are duplicated:

project = <YOUR_PROJECT> and issueFunction in linkedIssuesOf("", "is duplicated by")

To find issues that duplicate another issue:

project = <YOUR_PROJECT> and issueFunction in linkedIssuesOf("", "duplicates")

To find BOTH issues that duplicate and issues that are duplicated:

project = <YOUR_PROJECT> and (issueFunction in linkedIssuesOf("", "is duplicated by") or issueFunction in linkedIssuesOf("", "duplicates"))
Legna Garcia Mar 27, 2018

Hi there,

I think you really need a plug-in. I tried in cloud version and this was the result message:

Unable to find JQL function 'issueFunction'

Any plug-in available for cloud version?

Regards.

Like # people like this
B Mar 27, 2018 • edited

Hi Legna,

The ScriptRunner plug-in can enable the issueFunction capability in the cloud version. 

Please see:

https://community.atlassian.com/t5/Marketplace-Apps-questions/Substitute-for-issueFunction-in-JIRA-cloud/qaq-p/613278

Regards,

Brandon

David Russell Oct 25, 2018

That's a plugin.  Your original answer said it doesn't require a plugin.

Like # people like this
1 vote
Ian Price Dec 31, 2018

I'm forever coming up against the answer "You have to install this paid plugin" The cost of these can massively exceed the original of the original system.

This is like buying a car and then having to shell out for wheels as an 'optional extra'

 

Anyone fancy joining me in creating an Open Source version of Jira?

 

The aim would be to fix the many plugin issues as well as basic functionality issues like being able to add users permissions in bulk but having to delete the same permissions one by one...

0 votes
Shawn Wallack Jun 15, 2017

The problem with JQL Tricks "linkedIssuesInQuery()" solution is that every single issue needs to have the link type. It would be better if there were an option to have the link type applied at the epic level and have the query return the epic and all its constituent child issues and their subtasks.

For example, this filter:

(issue in parent("issue in linkedAllIssues(CH-58,\"contains the scope\")") OR issue in linkedAllIssues(CH-58, "contains the scope") OR issuekey = CH-58)

returns everything with a direct link to CH-58. But it fails to retrieve the child issues and subtasks belonging to those directly linked issues. I have not found a way to return the children of this result set.

It is not practical to link every single issue or subtask directly.

0 votes
Charis Jun 21, 2017

My company also is experiencing issue with linkedIssue. 

  issueFunction IN linkedIssueOf("key=TEST-111", "additional child of") returns rows as expected, say TEST-999. 

But doing the reverse query doesn't work, I was expecting that it should return TEST-111, but instead returns the following error:

   issueFunction IN linkedIssueOf("key=TEST-999", "additional parent of")

Error msg "Could not find any issue link type having either inward or outward description: additional parent of. Remove argument to search all link types. Available links are: [additional parent of , additional child of, Cloned from, Cloned to, duplicates, is duplicated by, is Epic of, has Epic, parent of, child of, Post-Mortem, Incident, depends on (deprecated), is depended on by (deprecated), causes, is caused by, relates to]"

 

Is anyone else experiencing this? How do we fix this? 

Thank you. 

 

 

 

Michael Sedovic Oct 23, 2018

i had the same issue and the solve was to make sure the text is exactly the same. In your instance do you call it "additional parent of" or just "parent of". we do the latter and it worked fine.

0 votes
Marika Feb 19, 2018 • edited

I figured the subject is the same so I'll post what I found as a result of this thread. 

In a very hacky way, I wanted to make swim lanes in my board that would display children hooked up to a parent using "is refined by" links. 

The description of the swim lane would contain the name and description of the parent. Then the JQL would be:

 

project = <project_name> and issuetype = Story AND issue in linkedIssues("JIRA-XX", "Is refined by") ORDER BY summary ASC

 

Worked a treat. Now every time a child is hooked up to a given parent using "is refined by" the board will update. 

Marianne Miller May 24, 2018

I think you can see linked issues if you add the column in the filter view.  Build the view for your project and then click "columns" search for "Issue Link" and then re-arrange it to the appropriate spot in your filter view.  I've found this very helpful for keeping up with active work.

0 votes
Brian Collins Jun 19, 2018

issue in linkedIssues("KEY-123")

0 votes
Nicholas Cafaro Jun 20, 2018 • edited Sep 18, 2018

hey folks just found a solution that is a pretty quick way to get what you need without a plugin:

1) Search for the issues that you want to find out if they have dependencies (i.e. by Sprint, Status, etc)

2) Click on "Columns" and select Links

  - this displays all the issues with Links (will include stories too but it's a good start)

3) Export CSV (with current columns)

  - this gives you an excel sheet that unfortunately includes each linked issue as a different column for each issue row record

4) Next to the last column used in the export, create a formula with the CountA(put range here) function and for the range start with the first column that contains linked issues and go to the end)

5) Filter the final column you just created and filter out the rows with 0 linked issues.

It's not perfect but it's a very quick way to scan through a large set of issues.  Alternatively you can just scroll through the JIRA search results using the added "Links" column to see if any stories have Linked issues.

Christine Ritchie Jul 24, 2018

but you don't know what kind of Link it is... that's not included in the output. We have many kinds of Links.

Tonya Birch Oct 24, 2018

Nicholas, thanks for sharing!  This is definitely The Best Solution to use without the need for plug-in.  

0 votes
George Sopko Jun 21, 2018

Hey everyone, I was able to more or less pull this off via this:

project=MY-PROJECT <AND other things you might want> AND linkedIssue != ABC-123

Just choose your project and some other linked issue you don't care about. In my case would have been referring to the very first ever linked issue which was before my project even existed.

Scott Jacobs I'm New Here Mar 28, 2019

This returns projects with no linked issues. You might as well just not include the final parameter.

0 votes
David Abowitt Feb 13, 2019

Could someone help me with JQL for this type of request:

1st step - I want to create a report that looks at all of our project tickets and if a ticket has under issue links "Has RCA" present it and sorted by due date

2nd step - I want to evaluate based on number of hours recorded in the worklog of tickets exposed in step 1 multiply that by a value to get an generic idea of cost of the incident.

I haven't been able to expose via JQL 

0 votes
Musaev Zamir Feb 14, 2019
Maybe project = PUB AND issue in linkedIssues("PUB-11", "is detailed in")

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Jira

Try Jira Cloud for Outlook: Organize your work without leaving your inbox

Hi Atlassian community, My name is Max and I work on the product integration team at Atlassian. I am pleased to announce the early access program for the Jira Cloud add-in for Outlook. This add-in...

2,502 views 6 15
Read article

Community Events

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

Events near you