Jira issues ordering: sprint vs completed sprint

[Ewgenij Sokolovski]

I wrote my own issue filter with ordering. In the ordering clause I mention the sprint: 

ORDER BY sprint ASC 

 Now, I got one of my issueswhich is assigned to the current sprint but at the same time to an earlier sprint as "completed sprint". Resulting in the issue being on the top of all other issues in my ordering although it is not what I want. I want the ordering to consider only "sprint" assignment, not the "completed sprint" one. Is there a solution to this?

[Jimmy Seddon · Accepted solution]

Hi @Ewgenij Sokolovski,

You are correct.  when using 'ORDER BY' it is looking at the value(s) in the sprint field and placing them in order by the (in your case) smallest sprint value it finds.  Since the issue in question is a part of both an active sprint and a completed sprint it will display on the top of the list.

If seeing things displayed this way is not what you want, your best solution would be to close all issues at the end of a sprint and clone new ones for work that isn't complete. Your other options would be to remove incomplete items from the current sprint (that is to be closed) before moving it into the new active sprint.

I hope that helps!

-Jimmy

[Ewgenij Sokolovski]

I understand but why cant Jira differentiate between the completed and the running sprint? I mean according to the ticket view these are different fields.

[Andreia Fernandes]

Hello, please try add this to your jql query: sprint not in closedSprints()

[Ewgenij Sokolovski]

Hello, that one would just exclude the issue from the search result. But that is not the point. My point was just to consider the sprint attribute only for ordering issues. But the attribute "completed sprint" is apparently considered as well.