Search for blocked issues?

How can I do these two searches?

- All issues that are not blocked

- All issues that are blocked


4 answers

JIRA Tricks is a commercial plugin, taking one aspect of functionality that some find useful (but others may not) and extending it. Sure, maybe JIRA's built in JQL could offer more, but if JIRA was "everything to all people" then there would be no healthy plugin ecosystem - and I am betting that we would pay more for JIRA and probably only get new releases at a much slower rate.

The difficulty of getting plugins installed is where having a development instance of JIRA can be useful. It lets you try before you buy and lets your users decide whether something is worth paying for. That's exactly how I got JIRA Tricks rolled out into my own environment.

For what it's worth, I have also had excellent technical support for this plugin. Not only that, but an additional query that I asked for was implemented within two months. Well, I like to think that it was my idea.

Noone takes that credit away from you Mark ;)

0 votes

Depends on how you are defining "blocked"? Is it via linking?

Yes, issue linking.

You can try the JQL tricks plugin, which would let you search for issues with an inwards "blocking" link, but I don't think it will let you sub-search on the target of the link being resolved or unresolved.

As Jamie says, the JQL Tricks plugin can help here. Here's the page that documents the types of query that you are looking for:

Thus, something along the lines of

issue in hasLinks("blocks")

Then extend this with "linkedIssuesHasStatus" to further test to see whether the blocking issues are open (or whatever best fits your requirements).

Does anyone know why JQLT is not incorporated into JIRA natively? I see mention of this a lot, but I can't easily get plugins installed on the JIRA instance I normally use. It seems like this should be built in functionality with the other JQL functions.

Firstly, full credit to Jobin for spotting an opportunity and exploiting it. My client will most likely purchase it.

However, I agree that many of the functions should be natively supported. And I'm also concerned that, as I've mentioned in the past with the confluence "prettification" plugins like Zen, Atlassian won't bother improving in these areas.

Thomas Schlegel Community Champion May 08, 2012
Agree with you, Jamie. There are more and more plugins one should buy to get functionality that Atlassian should provide. By the way, Atlassian is increasing the license fee for Jira very much. Shouldn't something like JQL Tricks be included as a basic functionality ? Atlassian People, maybe you could think about it ;-)

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,397 views 15 19
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you