-
Bug
-
Resolution: Fixed
-
High
-
45
-
Severity 3 - Minor
-
67
-
Summary
When filtering issues by issueLinkType the results are inconsistent when using the != and NOT IN operators.
Steps to reproduce
1. Do an advanced search and compare the results when filtering all issues in a project and all issues in the same project excluding issues with a specific issueLinkType;
2. Issues in the project can be checked:
project in ("Project A")
3. Issues in a specific issueLinkType:
project IN ("Project A") AND issueLinkType = "relates to"
4. Now run with the != or NOT IN clause:
project IN ("Project A") AND issueLinkType != "relates to"
5. Try by including an IS EMPTY clause:
project IN ("Project A") AND (issueLinkType != "relates to" OR issueLinkType is EMPTY)
Expected results
The != or NOT IN operators should return the difference between the first and second queries.
Actual Results
The values are inconsistent.
Workaround
- For similar behavior to what would be expected results of an "IS EMPTY" or "IS NOT EMPTY" you can use the workaround noted in JRACLOUD-72795 and do a filter "!=" referance to a saved filter to exclude any issue with the set list of link types, like the following:
- Create a saved filter including a list of all the current link types EXE:
saved filter = issueLinkType in ("all", "of", "the Issue Link Type Names", "as a comma separated", "List", "using Both the" "Outward Description" "And" "Inward Description")
- Then in your final JQL:
Project = "Project A" AND filter != <filter_ID>
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
JRACLOUD-23030 Not equals operator (!=) excludes results with empty values in JQL
- Gathering Interest
-
- Gathering Interest
-
- Under Consideration
- relates to
-
-
- Closed
-
-
-
- Closed
-
- was cloned as
-
-
- Closed
-
- causes
-
LYNX-1142 Loading...
- is resolved by
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
[JRACLOUD-73640] JQL issueLinkType is inconsistent when using != or NOT IN operators
This is still broken. Is there a mechanism to ensure a issue is resurrected?
This functionality is still not working!! Please re-review and fix!!
This blocks the validation of our medical device. Please fix!
To list issues that do NOT have a specific link is absolute base functionality!
Minor severity? Not being able to trust the data returned in your query is not minor at all.
Especially that its inconsistent. I'd rather you show me no results at all than to show me wrong ones.
A quick word about this workaround:
Project = "Project A" AND filter != <filter_ID>
If the filter contains all the values you do not want, then you can expect NULL values from this query.
If you are okay with Null values for issueLinkType in your results then this workaround is fine.
But if you do not want these Null issueLinkType values in your results, you will need to use the other workaround.
Workarround not usable for automation purposes. So please fix
Although the work around works for me, it will be great if this function works as expected. I only found out about this issue by 'accident'. I guess there will be users that do not find out this problem....