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

            Daniel Rauf made changes -
            Link New: This issue has a regression in JRASERVER-71112 [ JRASERVER-71112 ]
            Eoin made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 481317 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3063097 ] New: JAC Suggestion Workflow 3 [ 3691505 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Gosia Kowalska made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 437707 ]
            Gosia Kowalska made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 419018 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2630473 ] New: JAC Suggestion Workflow [ 3063097 ]
            Gosia Kowalska made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 395498 ]
            Gosia Kowalska made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 393472 ]
            Kasia Derenda made changes -
            Current Status New: {panel:title=Atlassian Update – 13 April 2018|borderStyle=solid|borderColor=#ebf2f9|titleBGColor=#ebf2f9|bgColor=#ffffff}
            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|https://pl.atlassian.com/software/jira/download].

            *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|https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-operators-reference-939938745.html#Advancedsearching-operatorsreference-operators].

            To read about other capabilities we added in Jira Software 7.9, have a look at our [release notes|https://confluence.atlassian.com/jirasoftware/jira-software-7-9-x-release-notes-946034808.html].

            Cheers,
             Katarzyna Derenda
             Product Manager, Jira Server
            {panel}
            Description Original: {panel:title=Atlassian Update – 6 February 2018|borderStyle=solid|borderColor=#ebf2f9|titleBGColor=#ebf2f9|bgColor=#ffffff}
            Hi all,

            Thank you for all your votes and comments on this suggestion. Special thanks to all who filled in the survey on potential solutions.  Your votes and the accompanying comments provided more valuable context for our team.

            We have started work on adding wildcard functionality to versions in Jira Server and will be releasing it in one of the future Jira releases.

            Thank you again for all your feedback on this suggestion and we look forward to providing you with more updates as we make progress.

            Best,
             Katarzyna Derenda
             Product Manager, Jira Server
            {panel}
            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.             		New: 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.
            Kasia Derenda made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 321313 ]

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

                Created:
                Updated:
                Resolved: