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

It would be useful to sort issues on the Issue Navigator by the Sprint field

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

      It would be useful to sort issues on the Issue Navigator by the Sprint field. It is currently not possible to sort issues by this field.

            [JSWSERVER-7664] It would be useful to sort issues on the Issue Navigator by the Sprint field

            Martin (Inactive) added a comment - - edited

            This Suggestion has been implemented and is available in JIRA Agile 6.7 and later.
            https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.7+Release+Notes#JIRAAgile6.7ReleaseNotes-OrderJIRAsearchresultsbysprint

            Kind regards,
            Martin
            JIRA Agile

            Martin (Inactive) added a comment - - edited This Suggestion has been implemented and is available in JIRA Agile 6.7 and later. https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.7+Release+Notes#JIRAAgile6.7ReleaseNotes-OrderJIRAsearchresultsbysprint Kind regards, Martin JIRA Agile

            Thanks for the fast reply! I'll check this out.

            Vincent Pehrs added a comment - Thanks for the fast reply! I'll check this out.

            It was a script field, so you need to have the Script Runner installed. Then you can create a script field like this:

            def pe_sprint = getCustomFieldValue("Sprint")

            if (pe_sprint)

            { return pe_sprint.name[-1] }

            else

            { return None }

            or go crazy, like this:

            def sprint = getCustomFieldValue("Sprint")

            if (sprint) {
            def name = sprint.name[-1]
            date = name.split("
            (")[-1].split("-")[0]
            date_split = date.split("/")
            try

            { month = date_split[0].toInteger() day = date_split[1].toInteger() }

            catch(NumberFormatException)

            { return null }

            if (date_split.size() > 2) {
            year = date_split[2].toInteger()
            if (year < 2000)

            { year = 2000+year }

            } else

            { year = 2014 }

            start = year*10000+month*100+day
            return start
            } else

            { return null }

            Jon Wynacht added a comment - It was a script field, so you need to have the Script Runner installed. Then you can create a script field like this: def pe_sprint = getCustomFieldValue("Sprint") if (pe_sprint) { return pe_sprint.name[-1] } else { return None } or go crazy, like this: def sprint = getCustomFieldValue("Sprint") if (sprint) { def name = sprint.name [-1] date = name.split(" (") [-1] .split("-") [0] date_split = date.split("/") try { month = date_split[0].toInteger() day = date_split[1].toInteger() } catch(NumberFormatException) { return null } if (date_split.size() > 2) { year = date_split [2] .toInteger() if (year < 2000) { year = 2000+year } } else { year = 2014 } start = year*10000+month*100+day return start } else { return null }

            Hi Jon,

            What type of customfield did you use? I tried to copy from Sprint to a short textfield but it gives me something like this: com.atlassian.greenhopper.service.sprint.Sprint@3b816cec[rapidViewId=428,state=FUTURE,name=44,startDate=,endDate=,completeDate=,id=406]

            JIRA 5.2.8 here

            Vincent Pehrs added a comment - Hi Jon, What type of customfield did you use? I tried to copy from Sprint to a short textfield but it gives me something like this: com.atlassian.greenhopper.service.sprint.Sprint@3b816cec [rapidViewId=428,state=FUTURE,name=44,startDate=,endDate=,completeDate=,id=406] JIRA 5.2.8 here

            We did this and it worked just fine.

            Jon Wynacht added a comment - We did this and it worked just fine.

            Here is a possible workaround by the time the Jira development team decides how to scratch their backsides.

            Create a custom field called "SortSprint".
            Use a post function to copy actual sprint numbers of any issue types through any transition as well as creation and edit to the "SortSprint" field.
            Include the Sort Sprint field in your screen schemas.
            Use sortsprint field to sort by sprint.

            P.S. this is just a high level idea. needs to be tested. So be careful.

            Biret Agirtan added a comment - Here is a possible workaround by the time the Jira development team decides how to scratch their backsides. Create a custom field called "SortSprint". Use a post function to copy actual sprint numbers of any issue types through any transition as well as creation and edit to the "SortSprint" field. Include the Sort Sprint field in your screen schemas. Use sortsprint field to sort by sprint. P.S. this is just a high level idea. needs to be tested. So be careful.

            Another +1. Rally has a view where one can display a list of user stories and Iteration is a sortable column. This was a useful view for me with Rally and it is one of the first things that I've missed since I've started using Jira.

            Csaba Körmendy added a comment - Another +1. Rally has a view where one can display a list of user stories and Iteration is a sortable column. This was a useful view for me with Rally and it is one of the first things that I've missed since I've started using Jira.

            Another +1. Pretty frustrating that our teams can't sort by this. Makes longer-term planning that bit more difficult.

            Sean Horgan added a comment - Another +1. Pretty frustrating that our teams can't sort by this. Makes longer-term planning that bit more difficult.

            Another +1. I work in a development team, often on different sprints simultaneously, and the ability to sort and organise my tasks as flexibly as possible is crucial.

            Mark Jackson added a comment - Another +1. I work in a development team, often on different sprints simultaneously, and the ability to sort and organise my tasks as flexibly as possible is crucial.

            I think it's quite embarrassing that an issue like this can be left unanswered for such a long time.

            Users should be able to sort by ALL agile fields.

            Nadia Tosheva added a comment - I think it's quite embarrassing that an issue like this can be left unanswered for such a long time. Users should be able to sort by ALL agile fields.

              Unassigned Unassigned
              cgauterio Clarissa Gauterio (Inactive)
              Votes:
              113 Vote for this issue
              Watchers:
              78 Start watching this issue

                Created:
                Updated:
                Resolved: