nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JQL issueLinkType != duplicates is not returning anything

Caldwell Clarke

Hi all,

I'm trying to filter out any duplicate bugs. Right now, my JQL query is:

labels = Alpha AND status in (Assigned, "Believed Fixed", "In Review", Incoming, Verify) AND issueLinkType != duplicates ORDER BY created DESC

This returns absolutely no issues, and I know for a fact that I have multiple issues that either have no issue links or are just "relates to".

The opposite does work. Replacing the != with = does properly return all the issues listed as duplicates.

labels = Alpha AND status in (Assigned, "Believed Fixed", "In Review", Incoming, Verify) AND issueLinkType = duplicates ORDER BY created DESC

Accepted answers

Petter Gonçalves

Hello @Caldwell Clarke

Welcome to the Atlassian Community!

Indeed, the parameter "issueLinkType" return inconsistent results when using the operators "!=" and "NOT IN". We created the following bug to fix this unexpected behavior:

JQL issueLinkType is inconsistent when using != or NOT IN operators

Feel free to vote and watch the bug to increase its priority and also receive notifications about its fix implementation.

As an option, you can use the workaround noted in JRACLOUD-72795 and do a filter "!=" reference to a saved filter to exclude any issue with the setlist of link types, like the following:

Create a saved filter including a list of all the current link types:

issueLinkType in ("is blocked by", blocks, "is cloned by", "is duplicated by", "is caused by", "relates to")

Then in your final JQL:

Project = "Project A" AND filter != <filter_ID>

Let us know if you have any questions.

All comments

Mathis Hellensberg

Hi @Caldwell Clarke

Have you tried issueLinkType in (duplicates) or changing the order? I can't see why that would work any better than what you have, but it is worth a shot

Caldwell Clarke

tried reordering for both issueLinkType != duplicates and issueLinkType not in (duplicates). No luck

Petter Gonçalves

Hello @Caldwell Clarke

Welcome to the Atlassian Community!

Indeed, the parameter "issueLinkType" return inconsistent results when using the operators "!=" and "NOT IN". We created the following bug to fix this unexpected behavior:

JQL issueLinkType is inconsistent when using != or NOT IN operators

Feel free to vote and watch the bug to increase its priority and also receive notifications about its fix implementation.

As an option, you can use the workaround noted in JRACLOUD-72795 and do a filter "!=" reference to a saved filter to exclude any issue with the setlist of link types, like the following:

Create a saved filter including a list of all the current link types:

issueLinkType in ("is blocked by", blocks, "is cloned by", "is duplicated by", "is caused by", "relates to")

Then in your final JQL:

Project = "Project A" AND filter != <filter_ID>

Let us know if you have any questions.

Caldwell Clarke

Got it. Thank you!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software