I was excited to see that the Jira Cloud now supports JQL queries with issueLinkType.
The following query gives me all Story tickets related to another ticket:
type = Story AND issueLinkType IN ("relates to")
However, I can't get the opposite, Story tickets that are not related to other tickets, when I use the following JQL
type = Story AND (issueLinkType NOT IN ("relates to") OR issueLinkType IS EMPTY)
Instead, the above gives me all story tickets. Any idea what I'm doing wrong?
Community moderators have prevented the ability to post new answers.
I found a workaround that seems to work:
type = Story AND issueLinkType in ("is tested by")save this filter and note the filter ID from the URL
filter != <filterID>
You may have to add some more conditions to the second filter.
This is absurd, but it works. :)
where 14697 below is the i.d. of a saved filter including the issues with the link I don't want -- AND issueLinkType in ("relates to") as well as the same JQL used in the second lookup below:
filter!=14697 AND project = XYZ AND type = "Resource" AND Status != Done AND "Department" = "Security" ORDER BY created ASC
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You saved me a lot of time! Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You've made my year.
This workaround is just genius
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The not in / != bug seems to have been raised here: JRACLOUD-73640.
Go vote!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Kevin, it looks like this same issue of !=/NOT IN not working with issueLinkType was raised in JRACLOUD-25640, but there haven't been any updates since Nov. 11th.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kevin,
i too am glad to see this feature. I just ran a quick test and "seemed" to work for me.
this query - type = task and issueLinkType not in ("relates to") - returned 142 items
this query - type = task and issueLinkType in ("relates to") - returned 538
now I have not scrutinized the results and TBH would have expected many more than 142 in the first. the one big difference in your is that you are including empty which would i think return any issue w/o a link. is that what you were going for or do you want all issues w/ links that are not "relates to"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's odd, when I try the following I get no results back:
type = Story AND issueLinkType not in ("relates to")
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What I've actually done is created a new link type call "Tests" with "tests" and "is tested by" as directional links.
We use Zephyr to create test tickets in our Jira. In order to determine which user stories have test tickets associated I run the query:
type = Story AND issueLinkType in ("is tested by")
That query works great and we save it as a filter and use it on a Confluence page to report on Story tickets with tests.
But when I want to search for Story tickets that do not have tests attached, so informing the team we have a gap in test coverage, the following query does not bring me back any results:
type = Story AND issueLinkType not in ("is tested by")
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We're trying to accomplish the exact same thing now, but the "issueLinkType not in" part still doesn't work. Did you ever find a workaround?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.