Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements


  • Give kudos
  • My kudos


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

How do I filter issues that are blocked in JQL Edited

Hi All, I'm trying to write a JQL filter to only show me issues in a project that block other issues however when I run the query ...

project = XX AND resolution = Unresolved AND Flagged = Impediment AND issueLinkType = "blocks" ORDER BY priority DESC

...I also get issues back that are not blockers, but are blocked by other issues. Can anyone explain why?

3 answers

0 votes

You can use something like this

project = XX and resolution = Unresolved AND Flagged = Impediment and issueFunction in hasLinks(blocks)

Thanks, does this solution work without ScriptRunner though? I was hoping to avoid using it

Unfortunately this exact syntax is applicable only for SR

@chris I tested your query and it worked fine and only returned those issues which blocking other issues. 


Try to index your jira 

Strange, I'm trying to think what could be different about my setup

0 votes
Andy Heinzer Atlassian Team Oct 07, 2019

Hi Chris,

I think I understand the confusion here.  The issueLinkType is a relatively new JQL function, only available since Jira 8.0.0.  This will return to us any issue that has a link of that type.  However it does not tell us anything more about the linked issue itself.

The only reason I can think of as to why you might get JQL results for this query that do not appear to actually have a 'blocks' type link, is that your account in Jira does not have permissions to see the issue that this issue is linked to. 

When that happens, your account won't see the link itself, but the issue still does have at least one link of that type to another issue.  This could be as simple as lacking the Browse permission in that other project, or it could be more complex and be restricted by a security scheme, in which case you might have the project permissions, but lack the security level needed to see that linked issue.  Either way, it is possible that your JQL query can return issues that appear to you to have no such links of that type.

As for how you figure out what that issue might be, well that gets harder to do.  If you are not a Jira admin, I would recommend reaching out to your Jira admin to see if perhaps they get back some more details about the link type on that issue.  Then again, they might not want to reveal that data to you, but they could likely confirm that this is the situation at least.

I hope that helps to explain this behavior.  Please let me know if you have any concerns about this.


Thanks Andy, I'll give that a try

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

3,957 views 11 5
Join discussion

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