How to JQL query Detected in Release, Version Picker (multiple versions)

[Chris Kemp]

NB If my conversation with CoPilot is to believed, it is highly restrictive.

My current project has several releases which, as fairly standard, has sub releases.
Again, the format is fairly standard, currently on Release 14;
14.0.0.12-2198
14.0.0.13-2214
etc

Ideally, I would want to query ALL version 14 releases. My understanding is that you cannot use wildcards, so an attempt to use a 'fuzzy search' was tried using ~.
"Detected in Release" ~ "14."
This failed, and CoPilot replied

---

Thanks for the clarification! Since "Detected in Release" uses predefined values/entities (likely a custom field with a version picker or dropdown), Jira's JQL behaves differently — the ~ operator won’t work for partial matches on such fields.

---

I then progressed to an attempt using IN;

project = "myProject" AND issuetype = Defect AND "Detected in Release[Version Picker (multiple versions)]" IN ("14.0.0.12-2198", "14.0.0.13-2214") ORDER BY key ASC, created DESC

This confused me, as it returned no results :(

After further discussion with CoPilot, I was informed

---

Jira strictly validates values in version picker fields. If any value in the IN clause doesn't exist, the entire query fails — even if other values are valid.

---

Surely the above must be the most basic requirement for reporting on versions?

If it isn't clear, I  want to report on all version 14 (sub) versions.

What I have found is, I cannot report on a wildcard or fuzzy search.
Also, I can only query on the values that will be returned by the query, effectively, I must only search on results KNOWING THE RESULTS(!?!?!?!)

To reiterate, I may query using "14.0.0.12-2198" and "14.0.0.13-2214", being two of the versions created in Releases, BUT if my date range does not have either one, the query will result in NO MATCHES (despite the date range having matches for one version)

Is CoPilot correct to say that this simply is not possible?

[Staffan Redelius]

Hi @Chris Kemp 

Just to clarify, I understand the field "Detected in Release" you are using is a custom field created within your organization and not the native fixVersion/affectsVersion?

If i do a search in one of our projects with the JQL project = [projectkey] and fixVersion ~ "25.*" i get all the issues in the project related to release 25.01, 25.02, 25.03 and so on. 

It might be a difference in how Jira treat different type of fields but try to change your JQL to: 

project = "myProject" AND issuetype = Defect AND "Detected in Release[Version Picker (multiple versions)]" ~"14.*"

Let me know if this helps!

Best regards,
/Staffan 

[Chris Kemp]

TBH I have no idea if it is a custom field, I have always assumed it was 'native' to Jira Cloud, as it has always been available within our projects.
Is there a way to determine if it is custom, noting that I am not a 'global' Jira admin for the organisation?

NB your suggestion looks very much like my attempt to use ~, however, I will try again when I am back at work tomorrow :)

[Cristiano Alves -Appfire-]

Hello @Chris Kemp ,

I'm Cristiano, with the Appfire team here.

It's weird that the "~" operated failed to return anything at all, although it would return any version with a "14" on it (like versions 2.0.14.25 for example)

In native Jira the affected version query with an ">=" will only work if the input is a version name directly (14.0.0), but this only works if the release order is configured and ordered to properly work.

To query with "in", yes, you will need the specific version numbers.

If you're open to using third-party plugins, the app our team works, JQL Search Extension for Jira, you will able to query directly for the operator, even if it's not ordered. IE:

affectedVersionsReleased > 14

If you need any help setting this up, or any further question about the app, feel free to contact our support team.

Regards,

[Chris Kemp]

Thank you for the suggestion. Unfortunately, being a large corporate, end users such as myself have no ability to use third party plugins (I actually have no idea if the Jira product owners have a process to request plug-ins, but given the organisation changes since it was implemented, I doubt it!)