Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-24152

JQL - Add wildcard functionality to versions

XMLWordPrintable

    • 110
    • 5
    • Hide
      Atlassian Update – 13 April 2018

      Hi everyone,

      We're glad to announce that wildcard functionality for version fields was shipped with Jira Software 7.9. As some of you may have already noticed, 7.9 was released this week, and you can download it here.

      What we've built

      Whether it’s 9, 9.1, or any other derivative you’re looking for, you can now find it with a simple query that uses the ~ operator and an asterisk to indicate the location of unknown characters. 

      Version fields are:

      • Affected version
      • Fix version
      • Custom fields that use the "Version Picker".

      Note that for version fields, the CONTAINS “~" operator returns an exact match. For example, to find the version "9.0" only, you would use the following query:

      fixVersion ~ “9.0”

      To find all issues where the Fix Version field contains a wild-card match for version "9", e.g. 9.1 or 9.0.1:

      fixVersion ~ "9*”

      The DOES NOT CONTAIN "!~” operator can be used to exclude a specific version in your query.

      For example, to find issues where Fix Version is not "9.0", you should use the following query:

      fixVersion !~ “9.0"

      To find all issues where the Fix Version field does not contain any version from the 9.x line:

      fixVersion !~ "9.*"
       
      You can read more in the article on Advanced searching here.

      To read about other capabilities we added in Jira Software 7.9, have a look at our release notes.

      Cheers,
      Katarzyna Derenda
      Product Manager, Jira Server

      Show
      Atlassian Update – 13 April 2018 Hi everyone, We're glad to announce that wildcard functionality for version fields was shipped with Jira Software 7.9. As some of you may have already noticed, 7.9 was released this week, and you can download it  here . What we've built Whether it’s 9, 9.1, or any other derivative you’re looking for, you can now find it with a simple query that uses the ~ operator and an asterisk to indicate the location of unknown characters.  Version fields are: Affected version Fix version Custom fields that use the "Version Picker". Note that for version fields, the CONTAINS “~" operator returns an exact match . For example, to find the version "9.0" only, you would use the following query: fixVersion ~ “9.0” To find all issues where the Fix Version field contains a wild-card match for version "9", e.g. 9.1 or 9.0.1: fixVersion ~ "9*” The DOES NOT CONTAIN "!~” operator can be used to exclude a specific version in your query. For example, to find issues where Fix Version is not "9.0", you should use the following query: fixVersion !~ “9.0" To find all issues where the Fix Version field does not contain any version from the 9.x line: fixVersion !~ "9.*"   You can read more in the article on Advanced searching here . To read about other capabilities we added in Jira Software 7.9, have a look at our  release notes . Cheers, Katarzyna Derenda Product Manager, Jira Server
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      With the release of JIRA 4.3, users can now specify a fix or affects version with a wildcard symbol in the Quick Search box (eg ff:4.*). Would be great to have the same functionality in JQL.

            [JRASERVER-24152] JQL - Add wildcard functionality to versions

            Роман Саврулин added a comment -

            Why this doesn't work In cloud?

            Роман Саврулин added a comment - Why this doesn't work In cloud?

            Bobby Boruah added a comment -

            Why versionMatch don't have in Jira cloud. 

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

            Bobby Boruah added a comment - Why versionMatch don't have in Jira cloud.  fixVersion in versionMatches("keyword") doesn't work. The VersionMatch is not there in cloud  

            Ryan Saul added a comment -

            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?

            Ryan Saul added a comment - 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?

            Ofer Prat added a comment -

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

             

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

            Kasia Derenda added a comment -

            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

            Kasia Derenda added a comment - 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

            Kasia Derenda added a comment -

            Hi Everyone,

            Thanks for all your feedback and votes so far, we truly appreciate them. We're currently considering two solutions for wildcard searching of versions in Jira, and we'd really appreciate it if you could take the time to fill out our 2 minute survey to let us know your thoughts and preferences.

            https://goo.gl/forms/YCVxtmOnILfih3mr1

            Thanks in advance,
            Katarzyna Derenda
            Product manager, Jira Server

            Kasia Derenda added a comment - Hi Everyone, Thanks for all your feedback and votes so far, we truly appreciate them. We're currently considering two solutions for wildcard searching of versions in Jira, and we'd really appreciate it if you could take the time to fill out our 2 minute survey to let us know your thoughts and preferences. https://goo.gl/forms/YCVxtmOnILfih3mr1 Thanks in advance, Katarzyna Derenda Product manager, Jira Server

            Tommi Kyntölä added a comment -

            Thanks overdevest!

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

            Tommi Kyntölä added a comment - Thanks overdevest ! I've been waiting for that for quite some time.

            Jack Nolddor [Sweet Bananas] added a comment -

            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.

            Jack Nolddor [Sweet Bananas] added a comment - 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.

            Daniel Overdevest added a comment -

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

            Daniel Overdevest added a comment - fixVersion not in versionMatch('regex*')   - does the trick!

            Hugo Passos added a comment -

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

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

              lvysochyn@atlassian.com Leo
              jsloat John Sloat (Inactive)
              Votes:
              302 Vote for this issue
              Watchers:
              170 Start watching this issue

                Created:
                Updated:
                Resolved: