How to have ORDER BY to only have current Sprint taken into account

[Bertrand]

When ordering my task list, I am using following JQL query:

project IN (PRODUCTA, PRODUCTB)

and assignee IN (currentUser())

and statusCategory IN ("To Do", "In Progress")

and status IN ("In Design", "In Progress", New, Open, "In Review", "Not Ready for Testing")

ORDER BY Sprint ASC, Priority DESC

However, the Sprint order is not what I want :

As you see, the order is mixed up. Seems caused by the +1 items. Typically, 2026.04.06 +1 includes both 2026.04.06 and an older Sprint, which is the reason for the +1 to appear. The task was not done, shelved for some time, and brought back for next Sprint.

Is there a way to have the ORDER BY command only use the current Sprint value ?

[Victor Law - Ricksoft]

Hi @Bertrand

Welcome to the community!

As suggested by other community members, this is not currently possible with the native JQL function in Jira.

As an alternative, you might consider using Excel-like Bulk Issue Editor for Jira, which provides Excel-style sorting and filtering to help organize issues more flexibly.

Disclosure: I work for Ricksoft, the company that develops and maintains this app.

With this app, you can:

• Use spreadsheet-style sort and filter to control how issues are displayed

• Apply an Active Sprint Filter to show only issues in the current sprint

These options can help you avoid the limitations of ORDER BY Sprint and get a cleaner view of your data.

Thank you.

[Bill Sheboy]

Hi @Bertrand 

Short answer: that is not possible with built-in JQL features, and thus workarounds depend upon how frequently you need this type of search.

JQL does not have functions to filter / order by a specific value within a list field, such as Sprint.  There are several possible workarounds, depending upon how frequently you need this type of search and your willingness to spend time / money:

• Need this one time
  • Export the work items to a spreadsheet, and use spreadsheet functions / features to enable the sorting after extracting the latest Sprint name (as you appear to be using date-based sprint names)
• Need this often
  • Have money to spend
    • Investigate the Atlassian Marketplace for apps which extend the features of JQL for searches like this
  • Have time to invest
    • Working with your Jira Site Admin, create a custom field to track the current, active sprint for work items, adding that to the relevant projects.  Then add a couple of automation rules to set / clear the field.  Finally, use the built-in JQL features to search, order by, etc. on the custom field.

Kind regards,
Bill

[Arkadiusz Wroblewski]

Hello @Bertrand 

One issue can belong to both completed and incomplete sprints, so ORDER BY Sprint can behave unexpectedly for carry-over items. 

Jira sorts against the sprint values on the issue, which is why an item with an older sprint can jump higher than expected.

That's just not something what Jira JQL handles well out of the box for multi-value Sprint fields

jql functions 

You can try some Apps which providing Enhanced Search functions, but out of the box, your Use Case are Tricky.

[Bartek Szajkowski _ Orbiscend OU]

Dear @Bertrand

I'm Bartek, from Orbiscend OU (Argon App provider). If you are open for the third-party app, I would like to recommend to check our JQL Argon app.

JQL Argon Powerful Search 

You can use the currentSprint function to filter issues to only those in the current sprint, which effectively solves the ordering problem — if an issue belongs to multiple sprints, it only appears when it matches the current one.

Example:

project IN (PRODUCTA, PRODUCTB)
AND assignee IN (currentUser())
AND statusCategory IN ("To Do", "In Progress")
AND status IN ("In Design", "In Progress", New, Open, "In Review", "Not Ready for Testing")
AND (
issue in currentSprint("PRODUCTA Board")
OR issue in currentSprint("PRODUCTB Board")
)
ORDER BY Priority DESC

The board name in currentSprint("...") must be an exact, case-sensitive match. If your two products share one board, you only need one currentSprint() call. If they have separate boards, use the OR pattern shown above.

I hope my response is helpful to you.

Greetings 

Bartek from Orbiscend OU

[M Chandra Shekar]

Hi @Bertrand Add this  - (Sprint in openSprints() ORDER BY Rank) to your current JQL.

[Arkadiusz Wroblewski]

@M Chandra Shekar 

That will help if the goal is to show only issues from active sprints, but it does not really solve Bertrand’s sorting problem.

sprint in openSprints() is just a filter, and Jira still keeps historical sprint values on carried-over issues. So it does not make ORDER BY Sprint use only the current sprint.

If the query is used at all, it should be written as ... AND sprint in openSprints() ORDER BY Rank.

And there is one more catch: if parallel sprints are enabled, openSprints() matches All active sprints, not one single “current” sprint.

[M Chandra Shekar]

Hi @Arkadiusz Wroblewski @Bertrand expectation also Same he wanted to filter issues from active sprints by order sprints. I usually use  JQL I mentioned same.