Why this doesn't work In cloud?

Why versionMatch don't have in Jira cloud. 

fixVersion in versionMatches("keyword") doesn't work. The VersionMatch is not there in cloud  

This feature isn't working for us on Jira Cloud either. I'm a little confused why the announced feature would not work on the cloud instance. Is the cloud instance a second class citizen to the self-hosted one?

Thanks for implementing this! However, I cannot use it in Jira cloud... any idea when it is going to be available there?

The form linked in the above comment is no longer accepting responses. Thank you for all votes and comments. We are starting  development and the wildcard search for versions will be available soon.

Katarzyna Derenda
Product manager, Jira Server

Thanks overdevest!

I've been waiting for that for quite some time.

Hi everybody,
as Daniel Overdevest already pointed out versionMatches() custom JQL function does the trick.

If you are using Jira Server you can install the FREE app called JQL Booster Pack throught Atlassian Marketplace and use the requested functionality.

After install this app, you should be able to create a query using versionMatches() function, that will allow you to find fixed in or affected by versions which its name contains the desired word.

This is the complete information of this JQL function:

Description:

Perform searches based on versions which their name match with the provided regular expression.

Note:
This function uses Java native String.matches() method internally to determine the versions affected by the given expression.
See also, Pattern Java Class.

 

Syntax	versionMatches(regex)
Available since	v1.0.0-RELEASE
Supported fields	AffectedVersion, FixVersion, custom fields of type Version
Supported operators	IN , NOT IN
Unsupported operators	= , != , ~ , !~ , > , >= , < , <= IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED

Examples:

• Find issues affected by versions that ther name starts with 'v1' i.e. 'v1.1.0', 'v1.2', 'v1.1.6', etc:

affectedVersion IN versionMatches("v1.*")

• Find issues fixed in versions that ther name contains 'alpha':

fixVersion IN versionMatches(".*alpha.*")

• Find issues affected by versions that ther name starts with 'SNAPSHOT' i.e. 'v1.1-SNAPSHOT', 'v1.5-NIGHTLY_SNAPSHOT', etc:

affectedVersion IN versionMatches(".*SNAPSHOT")

 

Kinds regards.

fixVersion not in versionMatch('regex*')   - does the trick!

Agree, allowing to query in the JQL for FixVersion LIKE 'X.Y.*' is almost a must.

So tired of modifying my filters and to add maintenance build versions!!! Please add wildcard support for JQL.

All I want to do is AND FixVersion LIKE '8.1.*'

There is an automatic completion for version texts, when entering version text to query. But that seems useless, as I know what versions I have. I would like to enter a wild card search to include future versions in queries of boards. It is currently like I try to insert wild card, but it doesn't accept, then the program suggests to try some other versions, but future versions are still missing from the query. So the autocompletion doesn't help.

I'm a release manager and there's a lack of basic functionalities to manage releases in Jira. Basically in a big company with multiple teams, projects and releases a week, Jira Versions to manage releases is just not enough. I’m surprised these basic functionalities have not been implemented yet:

-Create a jiraVersion with tickets from multiple projects

-Improve search for releases (For example, allowing the use of wildcards for fixVersions field)

-Release reports (Consolidated list of releases across all the projects)

-Custom relase notes templates.

-Custom release fields.

-Improve the way to edit, maintain releases

So tired of modifying my filters and to add maintenance build versions!!! Please add wildcard support for JQL.

All I want to do is AND FixVersion LIKE '8.1.*'

very much needed. how to manage versions in a complex software management (we have 300 components ++) otherwise? in the moment this is a mess and we are thinking about moving away from JIRA.

+1 

Obviously needed feature

What needing that too, will need to implement a service just to do this filter ! 

Just adding another plea to the long and ancient list - this would be a huge time saver. I'm already doing a convoluted workaround to get specific fix versions to appear on a dashboard and really don't need any more manual work to keep this up to date. PLEASE FIX ASAP!!

how many years must go by before someone cares to take the time to address this?

All voters and watchers,

I'd like to provide you with an update on this suggestion.
Despite we believe it's a valuable feature, currently there are no plans on our roadmap to address it.
We'll keep getting back to this suggestion to revisit it in the future.

By looking at some comments, it looks like some of the requests that come up there might have been solved. Please take a look at this documentation: https://confluence.atlassian.com/jiracoreserver073/advanced-searching-functions-reference-861257222.html?_ga=1.159777525.958568186.1466406441#Advancedsearching-functionsreference-unreleasedVersionsunreleasedVersions()
There are some functions that might help:

• releasedVersions()
• unreleasedVersions()
• latestReleasedVersion()
• earliestUnreleasedVersion()

Thanks,
Jakub Lazinski
Product Manager, JIRA

Thanks Hans! I concur your post!

Come on. The first request was done in 2011. How many more customer requests do you need to fix this? Obviously you guys @ Atlassian don't get the point. If we can use a wildcard in JQL, we can write a Confluence page that always shows what versions are (un)released. No more manual work, always up to date. Please. Fix. Now. (so that it works also for the cloud version). Great post, Tara Gangi!

This is highly needed; I am managing a program in JIRA and around 40 boards (within one project). We break out releases into major/minor which user stories get deployed in different environments. the Swimlanes are helpful in organizing which environments the teams need to work on, which are specified via fix version.

I needed this requirement implemented by AppFire, but they stated the functionality isn't there yet. It would be great if Atlassian could make this feature possible!

Improvement: board Swimlanes wild search

1. How can we have anyFix/Version that has the word "Maintenance" in it show in the Minor swimlane column (so i don't have to update them all the time with the respective FixVersions)

2. How can we have anyFix/Version that has the word "Release" in it show in the Major swimlane column (so i don't have to update them all the time with the respective FixVersions)

What is the solution if we run JIRA on jira.com?

All voters please consider to vote for JRA-19775

versionMatch() is currently in the Atlassian docs for Advanced Searching but with no description
https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-FixVersion

Unfortunately Script Runner is not free now.

Aww, common, how come this issue is opened more than 4 years now.
And there is no plugin that does it for JIRA Cloud.

Hello,

You can use versionMatch function of ScriptRunner plugin like this.

versionMatch("^(CC-|)15.*.0")

This will cause all version selected which fulfill the following conditions:

• Prefixed with either CC- or nothing
• Version suffix is build as follows 15.[anything].0

So would match:

• CC-15.x.0
• CC-15.4.0
• 15.4.0
• ...

This is part of an external plugin and not part of JIRA core, but ScriptRunner plugin is an usefull tool I can personally recommend.
And its for free (https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions)

Could Atlassian please provide feedback on this issue? We aswell would very much like to see this feature implemented

Vote Added!

In addition to this there needs to be a way to search for all versions between two given versions. Something similar to how you can search between dates would be perfect. Currently this isn't possible because you can't search for release dates in JQL either!

Vote added!

Vote Added!

Vote added!

Vote added!

Vote added. Could use it ( and we're on Cloud as well).

Any update on this one?

Any update on this one?

Ditto@ Michael Sica - we are cloud and can't use any of the work arounds

Really need this, and we can't use Script Runner because we're "cloud". Please add this!

Not a single update by Atlassian (apart from linking other issues) on this issue even after garnering 100+ votes?
At least Atlassian can tell us whether this feature will be available or not. Or at least, there can be an official information stating that this feature will be available via a commercial add-on.
However, I feel this should be a built-in feature and users shouldn't be buying an add-on for a basic functionality you would expect.
This is open for nearly 3 years.

Script Runner adds the missing support:
https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner

This is a basic requirement. I am surprised this hasn't yet been added.

Atlassian please consider this request.

I'm trying to use this on the Sprint field. We have different teams under a program which we're rolling up into a program board. Need to be able to simply say: Sprint ~ "Sprint 12*" and it should pull up all team's (different project) Sprint 12.

I represent about 100 votes from Navis.

We're using JQL Tricks now; yes commercial, but it works as advertised

Any progress on this requirement? And found that suggested plugin is commercial one

Thanks Mark on the plugin info. My problem, I have version listed custom fields that I need to search and this plugin only works for the fixVersion field.

There now seems to be a work-around available... the JIRA Tricks Plugin:

https://plugins.atlassian.com/plugins/com.j-tricks%3Ajql-plugin

..has recently added a new query function "versionMatches(regex)".

The specific documentation is here:

https://studio.plugins.atlassian.com/wiki/display/JQLT/Versions+Functions

fixversion in versionMatches("Release 1.0.*") - Returns all issues in versions with names starting at 1.0 like 1.0, 1.0.1, 1.0.2 etc.

The function was introduced in v3.0.1 of the plugin so that means that JIRA v5.0+ is required.

This might be a nice workaround but J-Tricks is a commercial plugin... so I am not withdrawing my +1 vote on this issue. =)

Can someone from Atlassian let us know when we may expect this issues to get resolved?

Voted. Wildcards or the "~" operator, as neither currently work with the fixVersion field.

I was very disappointed to find out wild cards don't work for fix versions. Hope they are going to add it.

Voted for this issue , I need the wildcard for compentent .

BR
Yossi

Yep, this would be a great feature. I was surprised that it didn't work for the popular FixVersion field.