Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-7860

Allow ordering by sprint in Jira Search

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • 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.

      When using the query

      order by Sprint

      it shows me the following error:

      Field 'Sprint' does not support sorting.

      Can we allow sorting by sprint (taking into account the dates of sprint).

      Use case: you can create the "to do" list for users or specific user taking into account the sprint of the issues and not just priority of fix version.

          Form Name

            [JSWSERVER-7860] Allow ordering by sprint in Jira Search

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3066804 ] New: JAC Suggestion Workflow 3 [ 3661281 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2622830 ] New: JAC Suggestion Workflow [ 3066804 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2322207 ] New: Confluence Workflow - Public Facing v4 [ 2622830 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2041397 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2322207 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2029594 ] New: JIRA PM Feature Request Workflow v2 [ 2041397 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 736576 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2029594 ]
            Martin (Inactive) made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 498080 ] New: JIRA PM Feature Request Workflow v2 [ 736576 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]

            Adrian Bridgett added a comment -

            Another nail in the coffin for JIRA. This sort of amateurish design (followed by a complete lack of action) is dreadful.

            More helpfully, you need to check the customfield table to see what the correct ID is to use:

            select id from customfield where cfname = 'Sprint';

            e.g. this returned 10005 for us so we used customfield_100005. Many thanks Gregory!

            Adrian Bridgett added a comment - Another nail in the coffin for JIRA. This sort of amateurish design (followed by a complete lack of action) is dreadful. More helpfully, you need to check the customfield table to see what the correct ID is to use: select id from customfield where cfname = 'Sprint'; e.g. this returned 10005 for us so we used customfield_100005. Many thanks Gregory!

            Michael Tokar added a comment -

            Many thanks for reporting this issue. We see it as a valid feature request however we cannot provide any guidance at this time as to when, or if, we'll be implementing it.

            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - Many thanks for reporting this issue. We see it as a valid feature request however we cannot provide any guidance at this time as to when, or if, we'll be implementing it. Regards, JIRA Agile Team

              Unassigned Unassigned
              63a7223e2adf Roman
              Votes:
              27 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: