Hi! I have a query that checks unblocked tickets; I use a similar JQL statement to the one posted previously:

issueFunction in linkedIssuesOf("resolution != Unresolved", "blocks") and resolution = Unresolved

One of my tickets has multiple blockers and when just one of its blockers gets resolved (the other one is unresolved), the parent ticket appears on this query which it obviously shouldn't because its still blocked. Has anyone else experienced this same issue?

I have posted this question here too (if people feel its easier to discuss in another location):

https://community.atlassian.com/t5/Jira-discussions/Unblocked-ticket-query-fails-with-ticket-containing-multiple/m-p/1356620#M10966

James, you can do it with Adaptavist Scriptrunner but you can't do it without an add on and that's a pretty basic expectation for a ticketing system.

We have Scriptrunner and even with a paid add on, you don't enough.  Sure you can find what's blocked by or blocking a specific ticket, but you really can't report on it.  For example, if you want to get a list of issues that are blocked, and also list what's blocking them (because that's the obvious next question, all you can really get is the Key of the blocking issue.  Unless everyone using Jira has all of the keys memorized, you're going to need to at least see the Summary.  I'll clarify.

Issue Key: ABC-123

Summary: Write Code

is blocked by

Issue Key: ZZ-99

Summary: Build Environment

You can link these two to show that ZZZ-99 is blocking ABC-123

You can search for blocked issues (ZZZ-99 included) with something like this:

• issueFunction in hasLinks("is blocked by")

There is no field/column specific to blockers.  The closest you'll get is Linked Issues which has 2 problems:

1. It only returns the key
2. The column shows ALL linked issues regardless of why their blocked

So you get something like this back:

Key | Summary | Linked Issues

ABC-123 | Write Code | ZZ-99, FOO-444, etc.

You could reverse the search to look for blocking instead of blocked issues but you'll have the same problem with trying to see what's blocked.

I don't think most people are going to look for blocked/blocking information on an issue by issue basis.  Most of us run a query looking for a list of results, usually across several projects, and need the information to be easily accessible.  Instead, you have to click in to each issue and try to find the real information and then manually make a report out of that if you want to send information on.

+1

To clarify the comment above, that requires ScriptRunner for JIRA, documentation for issue links functions is here.

You can do this with JQL:

issueFunction in linkedIssuesOf("resolution is empty", "blocks") and resolution is empty

See Linked Functions for a bit more information.

+1
I need to be able to filter blocked issues out of my default kanban board view, so I'm only looking at tickets I can work on.

So bizarre that we can't ask Jira "Which tickets are blocking other tickets?".  That's probably the most useful thing one could ask a ticketing system.

Very surprised this doesn't exist.  This is a missing core feature.

This is a basic functionality any JIRA customer, who has more than one project running in Jira. 

It's not a rocket science to get this as standand feature in Jira- please get this done.

+1. I'm stunned this isn't already in JIRA Core or Software.

+1

+1 

If you have scriptrunner you can use it in query

project = <project>  status = Open AND resolution in (Fixed) and issueFunction in hasLinks("is blocked by")

I agree...we also just upgraded to 7.2.6 and are hearing the same frustrations in extracts...

• user type fields are referencing the username values and not the Full Name
• key field has lost the hot spot URL

Like the flexibility of having the CSV option (as it does resolve some other issues) but perhaps offer the Excel option as well.

Same here. I had to create a custom button for blocked by. This isn't ideal since you can't link a bug and leaves it up to the person to put a JIRA link into that comment box. The ability to filter blocked by and blocks is important for our team.

Please, please, please add this feature soon. Tracking blocking issues over large projects is an incredible pain in JIRA at the moment.

Sincerely,

Jenn, a product manager and project manager,  who is sad and confused by the lack of proper dependency tracking in JIRA. 

Wondering if there was an official update on this? I have a ticket that reports on the issue it's blocking.

Instead of simple query I require to add a special status to solve this simple issue.

Please reconsider 

Why refuse implementing such an obviously useful and needed feature?

I want this because I want (need!) to be able to color subtasks in a Board based on whether the subtask is blocked or not. Why oh why has this feature languished for 6 years?! What is wrong with your architecture that you cannot provide a generic query language that has access to all the data available in the database?

How is this not in place yet. +1 as well.

Same as Ben, I created an account to ask for this feature. It would really help for reporting & follow up.

This is also something which I have had many requests for.

I created an account to plus one this!

I need this feature, too.  Most of my time seems to be spent shaving yaks, and it's easy to get lost in the herd and not quite able to get back to where you started.  Being able to see all the little tasks that block bigger tasks would help enormously.

Please create add this feature!

Also waiting on this feature, would love to see this implemented, it would make life so much simpler for project management..

<sarcasm>Please don't implement this feature. I love having to manually comb through all blocked issues to find when they have reached a state that will enable my team to perform actions.</sarcasm>

Any updates to this? This would be such a great feature!

I would love to see that feature implemented. I need something that allows me to quickly identify blockers.

Yes, I've just tested it on Agile Backlogs Quick Filters and I also created a quick filter in the Issue Navigator and they worked fine.

However, there are issues related to saved filters based on SQL for JIRA:

filer = "<My SQL for JIRA based filter>"

This looks like not working when it is performed directly from the Issue Navigator Advanced Search View,however it works when it is used as argument in third party JQL functions expecting a saved filter as parameter. This looks like a no well resolved issue JRA-28834

@Pablo Can you use SQL for JIRA to create Quick Filters Or Issue Filters?

SQL for JIRA supports it:

issue in sql("
select i.key
from issues i inner join issuelinks l on l.issueid= i.id and jql='resolution != Unresolved'
where l.type='Blocks' and l.direction = 'inward'
")

If you are on Server edition you can use ScriptRunner, the query is:

issueFunction in linkedIssuesOf("resolution != Unresolved", "blocks") and resolution = Unresolved

Translation: from all issues that are resolved, find those that link to others with the "blocks" relationship, then filter those by which are still unresolved.

Docs: https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_linkedissuesof

I'm looking for a way to list all issues which were blocked by resolved issues. Then we know that these issues are not blocked anymore.

Can't believe there is no easy solution or way for that one, except by reviewing each issue individually which is very time consuming.

n.messerschmidt - you might find this Add-On useful
https://marketplace.atlassian.com/plugins/jql-pro

I've dropped a comment here

jamieechlin is there any way to use Script Runner to return any issues that are unblocked? I would need to include issues where the blocking issue has been resolved.

Basically the idea is to show the user any available issues that could be worked on at that moment (blocked issues cannot be worked on). I asked this question here as well.Thanks!

Any update on this? We need a solution for this in our ondemand instance. So all of the mentioned plugins are not working...

Also possible with the jql functions module in the script runner plugin.

Examples:

issueFunction in hasLinks("blocks")

or "is blocked by" to get issues with the incoming links.

To search by resolution just add an additional clause.

Docs: https://studio.plugins.atlassian.com/wiki/display/GRV/Scripted+JQL+Functions

Currently in beta status, but please try it out.

There is a ticket open to add JQL Tricks to the OnDemand hosted environment, so anyone who is interested, please vote on it: https://studio.atlassian.com/browse/JST-4710

Regarding that JQL Tricks Plugin....
Has anyone tried using "Filter Results" gadget on a dashboard with a filter created using JQL Tricks functions?
As soon as mine tries to load that particular widget on the dashboard, it hangs the system and requires a system reboot.
If anyone has experienced similar issues or has already found a workaround, I'd really like to know.

I also didn't found any clue to get this, see also the discussion on http://confluence.atlassian.com/display/JIRA/Advanced+Searching?focusedCommentId=235668334#comment-235668334

@Jobin Kuruvilla: nice hint! But JQL Tricks Plugin. The linkedIssuesHasStatus() function seems to get this!

Check out the JQL Tricks plugin. It has the link functions which might support this request.You can't search by resolution but you can search by status.

I'm looking for the same thing. Are we missing something?