-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
2
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
In JIRA 4, we have advanced capabilities for querying, but they still don't solve this need for us
- the JQL contains (~) operator doesn't work with Reported in Release or the other release fields, because it cannot search the labels for the enumerated values in the pulldowns - the contains operator only works on text fields
- the JQL < and > operators do work, but they return essentially "higher or lower in the select list than the specified value", not "all releases in a particular branch" or "earlier or later releases of this code branch", and its unclear how they handle new entries added at the end or in the middle of the selection list.
The ideal situation would be if the contains operator "did what I mean", facilitating queries like:
"Fix Version" ~ "HF" to find all issues fixed in a hotfix release (HF 1, HF2, etc)
"Reported in Release" ~ "9.0" to find all issues reported against any build of 9.0 (9.0.x, 9.0.32.2,etc)
Is there a workaround we could use or is this currently not supported by JQL? This feature would allow us to create dynamic filters instead of adding new options to the filter each time options are added to the field we want to search on.
- relates to
-
- Gathering Interest
[JRASERVER-21974] Contains search on select list field using JQL
I think in some cases you can apply the selected value to a "Create Variable" action within the automation sequence, and have more text operations available to the newly-created smart variable that wouldn't otherwise work on the dropdown reference directly.
Credit to https://community.atlassian.com/t5/Jira-Software-questions/Use-smart-values-on-customfield-dropdown-field/qaq-p/2128865?anon_like=2128883 for figuring this out.
The issueFieldMatch JQL function available with the ScriptRunner plugin allows you to query the values for any field using regex. I've used it for custom fields and the Components field. It's the closest option I've seen to applying the "~" operator to non-text fields in JQL.
In addition to Versions and Components, it would be very helpful to be able to use the "~" operator on custom field options, i.e. on the values for Select, MultiSelect, Checkbox, Radio, and related fields.
Deleted Account (Inactive)
added a comment - +1 on wishing this operator existed for Components 
MarkW
added a comment - Adding my vote and watch to this issue.
We are in an Enterprise environment so we will not be able to manage the list of components and versions. Each project admin will enter them. Each company project has a number assigned to it. This project can cross several applications. So admins could list versions as:
Add new user project SP0012345 or Add new user SP12345.
In addition to what others above listed, I need to be able to search for versions that contain SP0012345 or contain SP12345. This could also help us identify these variations and correct them.
The same applies for components.
MarkW
added a comment - Adding my vote and watch to this issue.
We are in an Enterprise environment so we will not be able to manage the list of components and versions. Each project admin will enter them. Each company project has a number assigned to it. This project can cross several applications. So admins could list versions as:
Add new user project SP0012345 or Add new user SP12345.
In addition to what others above listed, I need to be able to search for versions that contain SP0012345 or contain SP12345. This could also help us identify these variations and correct them.
The same applies for components. 
Evgeny Zislis
added a comment - This also affects the "Components" field, for example trying to find all components that contain a certain word. And there is another issue that reports that jql has no such thing as startsWith(), which is also very useful for both cases.
Evgeny Zislis
added a comment - This also affects the "Components" field, for example trying to find all components that contain a certain word. And there is another issue that reports that jql has no such thing as startsWith(), which is also very useful for both cases. 
Dan Rinzel
added a comment - The goal is to be able to use contains searches or an equivalent on the user-visible labels in the select list (in effect, as though the field was a text field), rather than force the select list to be in an order that allows < and > to always work or force filter builders to use elaborate IN/NOT in filter arguments, which have to be edited every time more options are added to the select list field.
Dan Rinzel
added a comment - The goal is to be able to use contains searches or an equivalent on the user-visible labels in the select list (in effect, as though the field was a text field), rather than force the select list to be in an order that allows < and > to always work or force filter builders to use elaborate IN/NOT in filter arguments, which have to be edited every time more options are added to the select list field. 
Functionality like this would be very beneficial for us. Please, how does it look like with implementation? Thank you.