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.

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)

else

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

catch(NumberFormatException)

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

} else

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

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.

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.

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.

Ditto to Scott's comment.

Hi, another +1 for being able to sort on ALL agile fields as team members managing issues across multiple sprints with different deadlines need this information sorted. Please could an Atlassian member comment with an update.

In Agile Classic we made a habit of creating Confluence dashboards for long running projects, for stakeholders that should not be expected to navigate the Agile tools. Since moving to the new Agile functionality we have struggled to create meaningful dashboards. One reason (of several) is the inability to sort stories by their sprint or epic.

This seems like an obvious expectation. The lack of movement is disappointing.

+1 for this as well. Looking at my large number of issues without being able to sort by the sprints is a limitation.

Instead of arguing which fields should be sortable, how about recognizing that ALL fields should be sortable and let the user decide how they want their data ordered?

+1 for being able to sort on ALL agile fields. Not being able to sort on epics is a real pain.

Using sprint ID is a start. However, it would be good to be able to sort on all the Agile fields... such as Epic link.

I agree, sorting by sprint ID is an acceptable compromise.

Sorting by sprint ID would be great, even adding a column for sprint ID (separate from sprint name) would be helpful.

Bump on this as well. Seems pretty weird to have a data grid of results and one can't click on certain columns to sort. I'd be fine with sorting by the Sprint ID (instead of the sprint description/name) if that was easier to implement

Could someone from Atlassian report on this ticket? This ticket was created over a year ago we haven't heard any progress reports in this or any of the related tickets.

Can we raise the priority of this?

I have several folks asking me as the admin for this Sprint field to be a searchable field. Thanks!

Hello,
Are you planning on implementing this?

Thanks,

Has there been any movement on this request? I have multiple project managers asking me for this request. The only workaround I have is to create a separate field that they must also manage along with the JIRA Agile board.

As someone else stated, sorting by sprint (and other agile-related fields) is important for reporting on a subset of issues via the jira issues macro in confluence. I don't think this is a minor improvement, it should at least be normal.

Our use case is to sort by Rank and order by each Sprint, otherwise the Rank file is irrelevant in context of a filter without specifying a specific sprint. In the days of yore we were using Fix Versions combined with the rank field, and they both could be sorted together, but the new sprint field isn't as capable as the fix version field.

Please add this feature. We use both Issuer Navigator and the addin Structure to work with hundreds of issues in different sprints.
We are really handicapped by lack of this basic, but ultra important feature (especially as Sprint id is a numeric field, I cannot see why it cannot be used it to order issues by).

I am disappointed and amazed why this is considered a minor feature!
What's the level of effort to develop this ?

In the last few releases of Greenhopper i've seen so many non critical, ui, cosmetic issues dealt with, but a major feature which affects every PM out there has not been dealt with this.

Our teams also work on multiple sprints at a time. I was very disappointed when I discovered that Sprint could not be used to sort or filter in the issues list. Please add sort and filter functionality for the Sprint field.

Hi Atlassian,

Rob from the Seattle office hit this. He wants to build a filter like: assignee = currentUser() and order by sprint

Rob wants to look at a filter of the results so he sees the whole context of many issues all at once, rather than using keyboard shortcuts or clicking on individual issues to find those details (Issue Detail View on the Agile Board).

Thanks,
Nicholas Muldoon

I'd like to be able to use the macro in Confluence to show the current sprint but if I can't filter this then I end up showing all issues.

It would effectively be very useful to be able to use the Sprint field as a standard on which we could sort normally.

my team needs this as our team members work on multiple sprints at a time. We have no good way of managing our to-do items across multiple sprints.