jira query: jql to find issues that have linked issues

[SallyD]

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?

[Andy Heinzer · Accepted solution]

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]

Good to know! Thanks!

[Marie F. Kent]

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

[Vik]

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

[Becky]

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).

[Andy Heinzer]

@Vik 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]

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... 

[Andy Heinzer]

@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]

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

[Andy Heinzer]

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]

This is our issue link type set up: 

[Andy Heinzer]

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

[Brandon]

@Andy Heinzer , is there a way to search for any blocking JIRA's in a certain project.

For example I want to see all JIRA's that I'm blocking, for another project not just a specific blocking JIRA. 

Does that make sense? 

Visually I'm thinking Project = XYZ and issueLinkType in (blocks, causes, (Project))

[Andy Heinzer]

Hi Brandon,

Natively, within Jira there is not a way to do that right now.  The JQL can only return to you Jira issues that contain at least one link type of a specified value.  It cannot tell you anything more about the linked issue values.  But perhaps what you are looking for is possible within Vidic's Answer on this page through the use of a plugin, and that plugin's JQL functions.

Andy

[Timothy Johnston]

@Andy Heinzer 

When I am using the below search I get items that are both blocking and blocked. 

issueLinkType = blocks

However, when I use "is blocked by" then I only get those items. 

I am using Jira Cloud. Any ideas? Known bug? Workaround? 

[Andy Heinzer]

Hi @Timothy Johnston 

Thanks for bringing this up. I took a closer look at how this feature is working. The issueLinkType is able to search by the Outward Description, the Inward Description, and the Name of the link type itself.  When you use the Name, it searches for both kinds of descriptions (inward and outward).  But using only one of the descriptions you only get back those results.

The problem with this is that the default for the Name "Blocks" also has an outward description that is also "blocks".  Since JQL doesn't handle case sensitivity here, you're actually always searching the name rather than the description in this case.  Which explains why you are getting the results you see here.  Since this is the only default linktype that has the same name as a description, I found it that I could workaround this problem by simply adjusting the link's outward description.  To adjust this I went into my Issue Linking settings in [examplesite].atlassian.net/secure/admin/ViewLinkTypes!default.jspa and then I changed by outward description from 'blocks' to 'blocking'.  This way you can then make distinct JQL searches for issues with that specific outward description and not just all the issues in the blocks name.

I hope that helps, but I agree that you have hit on something there that other users will probably also get stuck on again in the future, so I have created a feature request to change this default over in JRACLOUD-73372 (for Jira Cloud) and JRASERVER-70231 (for Jira Server). I don't think this technically is a bug, but I agree that a slight change could avoid plenty of headaches about this.

Cheers,

Andy

[Timothy Johnston]

Thanks @Andy Heinzer 

The reason I would classify it as a bug is that the JQL suggested text gives 'blocks' as the option. However, I do understand the case of not-a-bug as described above.

Thank you for the workaround / fix. 

[Christoph Böhmer]

Great news for us as well, that IssueLinkType can be used in JQL queries/ Dashboards.

We are desperately looking forward to our upgrade to JIRA 8.0 next year.

I haven't seen an answer yet on whether the issueLinkTypes can also be displayed as column in the filter results or used as statistic types in Dashboard gadgets, see post from @Marie F. Kent   ?! this is also a strong requirement for our usage.

@Andy Heinzer could you outline if it is possible with JIRA 8.0 Server to also display issueLinkTypes in filter results and dashboards ?!  

Thanks

Christoph

[AB]

@Andy Heinzer, adding to what Christoph mentioned above, can we have the possibility to view the issueLinkTypes of a ticket as part of the 'Columns' in the output of a JQL?

Currently this is not possible (at least in Jira v7.10.2), so, if a list of tickets are, in turn linked to other tickets with different link types, there is no way of knowing the link types of these tickets, without checking each main ticket individually. 

This is a LOT of work! There is already a request for this feature. Any idea if this has been accepted as a feature (and if so, what the link to and timeline for, it, is)?

For any JQL search, we need the possibility of viewing 'issueLinkTypes' as a column.

[Andy Heinzer]

Hi @AB and @Christoph Böhmer

Currently neither Jira Server nor Jira Cloud have the ability to display in the issue navigator columns these linktypes.  It can be made to show the specific issue link's issuekeys.  However for the feature I think you are wanting to see is most likely encompassed in the feature request JRASERVER-39413 for Jira Server, and JRACLOUD-39413 for Jira Cloud.

That said, at least in the Jira 8.7.0 version, if you were to use the export all columns as CSV, that CSV file does indicate the linktypes and link directions by column names.  This doesn't really help for the sake of trying to build a JQL filter for a report on that data directly in Jira, but the data is something that could be exported here.

I hope that helps.

Andy

[AB]

Thank you, @Andy Heinzer, for your very prompt response and helpful links!

From the feature requests you mentioned, it appears the feature is long-pending (requested 6.5 years back, as of this writing). One wonders a little, hence, why, their status is still 'GATHERING INTEREST'! How many votes would move it to REVIEWING and further statuses?

Apart from the above, I had another question. The feature description talks about 'users being able to see the link type of the linked issues in Issue Navigator'. However, it doesn't explicitly mention about the Issue Link Type being a separate column from the existing Issue Link column. At least one of the incorporated Jiras mentioned this, so I will try to reiterate this part of the requirement there.

Thanks!

[Brandon]

AB, 6.5 years in Atlassian time is relatively new actually.

We just recently had an issue that was opened originally about 15 years ago worked so don't fret. There are still many years ahead for this issue :)

[Andy Heinzer]

Hi @AB,

Please take a look at our Implementation of New Features Policy. It explains how we choose what features to implement. There is no magic number of votes needed to implement a new feature. The votes on JAC are important to us, but they are not the sole factor involved in determining which features get selected for development. For Jira Server, you can also get a good idea of what tasks are currently being worked on by the Jira Server/Data Center development team and see which items are in progress, under consideration, short-term backlog, etc by looking at the dashboard called Jira Server and Data Center: current work and future plans.

Thanks for pointing out that the JAC ticket I linked wasn't exactly what you were asking for here.  I can see why this separation of columns could be useful here.  I have actually updated the JAC ticket to reflect that detail in the summary and description.

Cheers,

Andy

[AB]

Thank you, @Andy Heinzer, for getting back regarding the New Features Implementation Policy and also for updating the ticket.

A related question, though: While this thread (and the JIRA tickets you so helpfully shared) are related to requesting a new column for the 'IssueLinkType', the request could be extended for other properties of the linked issue as well. For example, if I want to view what is/ are the 'FixVersion(s)' (if any), of the linked issues, or what is their 'Status' or 'Resolution', I can't. Would you be aware if this 'general extension' has also been requested?

Thanks!

[Andy Heinzer]

Hi @AB,

I think I see what you are looking for here. You are correct that Jira is natively not able to let you search on the linked issues fields when expected to return the source issue.  I found a few similar old requests, but all of these were closed out with the resolution "Won't Do" years ago. The most recent example I can find is JRASERVER-69124. 

While that one is specific to searching based on the linked issue's resolution field, it does have a work-around section where it is suggested that there exist 3rd party plugins to Jira that can help with this use case.  That community thread mentions two plugins by name: JQL Search Extensions and Scriptrunner, but I'm confident there likely exist several other add-ons in Marketplace as well that could also help provide the functionality I think you are looking for here.

[Adriana Gornea]

Hi @Andy Heinzer
can I also search for tickets that are linked by a specific ticket with a specific link type? 

For example, I have ticket 1 and by this ticket I have 2 tickets linked as "master of", 10 tickets as blocked, etc.. can i make a filter and see only these 10 tickets which are blocking this ticket?

Thanks,
Adriana

[Andy Heinzer]

Hello @Adriana Gornea 

If you happen to know the exact issuekey of your 1 ticket, then yes it can be done.  But you would need to use a different JQL function, namely linkedIssues().  This has a JQL syntax of

issue in linkedIssues(ABC-123,"blocked")

[Adriana Gornea]

@Andy Heinzerthank you. very useful.

[Damián Sánchez Moreno]

Once again, Jira disappoints.

[Vidic Florjan · Accepted solution]

You can prepare filter with JQL functions of the:

1. Script Runner plugin

Issue Links

- hasLinks(link name)

- hasLinkType(link type name)

- linkedIssuesOf(Subquery, link name)

2. Search Linked Issues for JIRA plugin: https://marketplace.atlassian.com/plugins/org.craftforge.jira.craftforge-jql-functions-plugin

3. JQL tricks plugin:

https://marketplace.atlassian.com/plugins/com.j-tricks.jql-plugin

[Vidic Florjan]

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

[Jeroen Vandeweghe]

So there is no way to do this without plugins?

[lade]

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

[Ed Guy]

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

[Joakim Borgström]

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]

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

[Marian Reynov]

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]

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]

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]

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]

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

[Marie F. Kent]

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

[Ed Vitalos]

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

[AJ Magcale]

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

[Deleted user]

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]

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

issue in linkedIssues(XXX-XX)

[Alan Williams]

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.

[Jon Bertrand]

+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.

[Attila Strba]

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 ...

[Mark Brogowicz]

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]

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

[Fabian_Schneiter]

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

[Katrin Kueper]

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

[Amol Baviskar]

+ 1 - cannot believe JIRA does not support this 

[Legna Garcia]

+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.

[Aurelie Navarro-Lee]

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

[Bhogesh Nimmala]

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

[nima.zeighami]

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.

[Somya Upadhyay]

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

This helped me resolve the issue.

[Charis]

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]

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>

[bthayer]

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:

[Allison Carlson]

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]

Perfect, THX, that helped ;)

[Damián Sánchez Moreno]

Looks like this is a ScriptRunner solution.

[Thu Trần Aroma]

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]

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.

[Daniel Turczanski - __JQL Search Extensions]

Hi,

It's an old post but it's worth to know that we offer a dedicated indexing service that gives you advanced support for Jira links:

• JQL Search Extensions

After you install the app you can search for issues that have links:

linksCount>0

and you can find issues that are linked to your particular subset of issues:

issue in linkedIssuesOfQuery("project=ACME", "is blocked by")

You can check out all the extensions in the docs.

I hope this solution is helpful!

[SUVARNA Dixit]

issue in linkedIssues(ABC-123,"blocked")
instead of specific story , would like to knows defects per story 
how we can use nested query instead of story id

[Stephen Burke]

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]

I totally agree 

[Filip Pokorny]

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]

@Filip Pokorny

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

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

[Filip Pokorny]

I just tried now and it works, 

JIRA v7.6.1 Server

[Christine Ritchie]

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

[Filip Pokorny]

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.

[lucy sogard]

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 Project, Issuetype = 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]

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)

[Ray Maxwell]

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.

[Hanna Blomqvist]

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

[Ian Price]

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...

[B]

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]

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.

[B]

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]

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

[JulienFritsch]

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]

just add the criteria like this

issueFunction in hasLinks("relates to") and resolution is not EMPTY

[lucy sogard]

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 Project, Issuetype = 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]

issueFunction requires ScriptRunner plugin

[Kate Asaff]

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!

[Darryl]

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

issue in hasLinks()

(JIRA 7.2.4)

[Ming Lam]

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

[Shanyn doCarmo]

@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]

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

[Kin]

I'm actually dissapointed that I cannot find a way to efficiently get the fixVersions for each issuelinks from each issue in a single JQL request.

[Musaev Zamir]

Maybe project = PUB AND issue in linkedIssues("PUB-11", "is detailed in")

[David Abowitt]

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 

[George Sopko]

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]

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

[Nicholas Cafaro]

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]

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]

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

[Brian Collins]

issue in linkedIssues("KEY-123")

[Marika]

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]

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.

[Charis]

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]

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.

[Shawn Wallack]

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.