Activity
Show:
Adrien RagotMay 4, 2021 at 7:09 AM
Since 2.6.0 for DC (and 2.5.7 for Server customers), we’ve introduced a custom field, which is both easier to search and, more importantly, reliable with the NOT keyword.
We won’t fix the old function, because it was not properly fixable (That is the reason we moved to a custom field).
Resolved
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Reporter
Requirement Yogi
Linked requirements
Linked requirements
Created October 31, 2019 at 9:32 AM
Updated April 10, 2024 at 8:34 AM
Resolved August 26, 2020 at 4:38 PM
What is delivered
The NOT keyword dysfunctions because there can be too many issues returned by the search criteria.
In 2.5.7, we've at least warned when the search criteria was returning many issues.
Original requests
We've had:
A US customer who said they want to use: `issueFunction not in linkedIssuesOfRemote("relationship", "implements")`
Another customer in contact with Salmane who said they want to use the "NOT" keyword too.
Apparently, Adaptavist had a working implementation with a JQL function: https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html
They've defined a custom field:
Could we do the same with our existing custom field?
Can our custom field be hidden from view?
They've defined an indexer:
How do Jira indexers work? Can we define our own?
What is the relationship between a Jira indexer and the JQL function, is it raw text, or can it be a Java object-based comparison relying on a function?
To note: We could recover the feature using our Traceability matrix, if the first column could be a Jira issue.