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

List Issues in Issue Navigator according to FixVersions regardless of Issue Key

XMLWordPrintable

    • 1
    • 4

    • 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.

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

      Problem Definition
      Currently in JIRA if users list issues according to the FixVersions, JIRA will be listing the Issues according to the Issue Key and after that according to FixVersions value. This is because versions are project specific and the sort order is defined by the arrangement of the project versions within the project configuration.

      Suggested Solution
      Allow users to sort issues by Fix Versions value even though they are searching for issues from multiple projects.

      Workaround
      Currently there's no workaround for this.

        1. FixVersions ORDER Bug.png
          FixVersions ORDER Bug.png
          533 kB

            [JRACLOUD-59992] List Issues in Issue Navigator according to FixVersions regardless of Issue Key

            Alis-Hathway Ward (DO NOT USE) added a comment -

            The issue occurs even when project is specified, so not a workaround. In any case, ordering by fixVersion only should sort by fixVersion only, whether you specify the project key or not. You don't order by createdDate and expect it to group by project without specifying project, so why should fixVersion be any different?

            We set fix version as follows: "x.x.x Web: feature" , or "x.x.x Apps: feature"

            Given

            project = JRACLOUD and status = "To Do" ORDER BY fixVersion ASC

            And ASC = "Go up" in Jira (as in, "ascending the stairs"):

            Observed:

            • 2.1.0 C:
            • 7.2.0 Apps:
            • 3.2.0 Web:
            • 7.3.0 Apps:
            • 4.0.0 Web:
            • 7.1.3 Apps:
            • (Null)

            *NOTE: Confirmed that it's NOT sorting by version release or start date instead of alphabetical, so those are not the source of this unexpected ordering. Null at the end of an ASC query is suspect, though. Almost looks like code collision, doesn't it?

            Expected:

            A-Z Sort

            • (Null)
            • 2.1.0 C
            • 3.2.0 Web
            • 4.0.0 Web
            • 7.1.3 Apps
            • 7.2.0 Apps
            • 7.3.0 Apps

            Given 3.2.0 Web & 3.2.0 Apps:

            • 3.2.0 Apps
            • 3.2.0 Web

            Alis-Hathway Ward (DO NOT USE) added a comment - The issue occurs even when project is specified, so not a workaround. In any case, ordering by fixVersion only should sort by fixVersion only, whether you specify the project key or not. You don't order by createdDate and expect it to group by project without specifying project, so why should fixVersion be any different? We set fix version as follows: "x.x.x Web: feature" , or "x.x.x Apps: feature" Given project = JRACLOUD and status = "To Do" ORDER BY fixVersion ASC And ASC = "Go up" in Jira (as in, "ascending the stairs"): Observed : 2.1.0 C: 7.2.0 Apps: 3.2.0 Web: 7.3.0 Apps: 4.0.0 Web: 7.1.3 Apps: (Null) *NOTE: Confirmed that it's NOT sorting by version release or start date instead of alphabetical, so those are not the source of this unexpected ordering. Null at the end of an ASC query is suspect, though. Almost looks like code collision, doesn't it? Expected : A-Z Sort (Null) 2.1.0 C 3.2.0 Web 4.0.0 Web 7.1.3 Apps 7.2.0 Apps 7.3.0 Apps Given 3.2.0 Web & 3.2.0 Apps: 3.2.0 Apps 3.2.0 Web

            Riya Sharma added a comment -

            Wouldn't a work-around be to specify the project within which to search?

            Riya Sharma added a comment - Wouldn't a work-around be to specify the project within which to search?

              Unassigned Unassigned
              vshanmugam Vicknesh Shanmugam (Inactive)
              Votes:
              43 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated: