JQL for the current sprint

Published 2026-09-24 by Sidecar Tools. Every JQL query and error message below was run against a Jira Cloud site on 2026-09-24. Automation steps use Jira's current "work item" wording; older sites say "issue".

Short answer

sprint in openSprints() ORDER BY rank ASC

openSprints() returns every sprint that has started and not been completed, across all boards you can see. Add a project clause if several teams share the site, for example project = KAN AND sprint in openSprints().

Everyday sprint queries

You want	JQL
Still open in the active sprint	`sprint in openSprints() AND statusCategory != Done ORDER BY rank ASC`
Carried over from an earlier sprint	`sprint in openSprints() AND sprint in closedSprints() ORDER BY rank ASC`
Created in the last two weeks and already in the sprint	`sprint in openSprints() AND created >= startOfDay(-14d) ORDER BY created DESC`
Backlog: open and in no sprint	`sprint is EMPTY AND statusCategory != Done ORDER BY rank ASC`
Planned for future sprints	`sprint in futureSprints() ORDER BY rank ASC`
Unestimated in the active sprint	`sprint in openSprints() AND "Story Points" is EMPTY AND type != Sub-task`

Notes that save time

Carry-over. A work item keeps every sprint it has been in. If it is in an open sprint and also in a closed one, it was not finished last time. This is the quickest way to see spill-over before a retro.
Scope added after the start. JQL has no "added to sprint after it started" field. The created-date query above is an approximation; the sprint report in the board is exact.
Estimates on team-managed projects. The field is called "Story point estimate" there, so use "Story point estimate" is EMPTY.
ORDER BY rank gives you the same order as the board.

Want the rest? The Jira Cloud JQL Cookbook has 66 copy-paste queries for triage, sprints, releases, SLAs and reporting, each one validated on Jira Cloud. Get it on Gumroad, pay what you want from $12.