Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-23170

Ability for JIRA to understand version hierarchies

    XMLWordPrintable

Details

    • 1
    • 2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      The idea is essentially the same as presented in JRA-846 but for versions instead of components ( http://jira.atlassian.com/browse/JRA-846?focusedCommentId=183746&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-183746 ):

       
[1]
  [1.0]
    [1.0.0]
    [1.0.1]
    [1.0.2]
  [1.1]
    [1.1.0-Beta-3]
    [1.1.0-CR-1]
    [1.1.0]
    [1.1.1]
[2]
  [2.0]
...

      The end result is simply to allow better version-based searching. To me there seems to be numerous ways to accomplish this (pattern recognition, hierarchy with explicit parent selection).

      Attachments

        Issue Links

          is duplicated by

          Suggestion - JRACLOUD-27781 Improve nested versions

          • Closed
          is related to

          Suggestion - JRASERVER-23170 Ability for JIRA to understand version hierarchies

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              85d0dc6fc42a Steve Ebersole
              Votes:
              27 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

                Created:
                Updated: