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
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:
issueLinkType in ("is blocked by", blocks, "is cloned by", "is duplicated by", "is caused by", "relates to")
Project = "Project A" AND filter != <filter_ID>
Let us know if you have any questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
tried reordering for both issueLinkType != duplicates and issueLinkType not in (duplicates). No luck :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.