You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
A common feature in Jira are Software boards - Kanban and Scrum boards are widespread in agile development.
While a Kanban board is a more simple approach with Scrum people usually work in sprints.
During the period of a sprint a team implements and delivers a discrete and potentially shippable application increment. This could be for example a working milestone version.
For new users a fixed duration of two-weeks for each sprint is common. Two weeks are long enough to get something accomplished, but not too long so that a team is able to get regular feedback.
In Jira Software, sprints are showed on a boards. Issues are to sprints using filters. You also can search for issues in upcoming sprints using JQL.
Today I am going to show you some useful JQL queries which you can use to query for issues. Those are often assigned to either a currently opened sprint, a completed sprint or a future sprint.
Additionally you learn how find issues in a specific project which are at the same time contained in a sprint.
Searching for issues is easy - you can navigate to "Filters" >> "Advanced issue search" from within your Jira instance.
While it is the possible to click on "+ More" and to select "Sprint" using the "Switch to JQL" button, which is a perfect option for new users to learn, you also can write your own JQL query.
As soon as you have created a sprint you can search directly by the sprint's name.
Sprint = "My sprint 6"
It will show you all issues that are contained in the sprint listed in the query.
In the example above you can see one issue assigned to a sprint "My sprint 6".
After their creation sprints it takes some time until planning work is done - therefore they are usually not started right away. Rather this happens when the team is ready - so sprints are considered being a future sprint right after their creation.
As soon as first issues were assigned to a future sprint you can query for them:
sprint in futureSprints()
Of course you can adapt this query. For example you can narrow it down to a project of your interest like this:
project = DEV and sprint in futureSprints()
This query will show all issues in project "DEV" that are assigned to future sprints.
As soon as a sprint is started you will want to use a different query.
A quite similar JQL query to the previous one will show you issues in open sprints:
sprint in openSprints()
Hint: depending on the configuration of your Jira instance it is possible that the feature "Parallel Sprints" is enabled. Doing so more than one sprint can be started at the same time.
If this is the case the query will show issues assigned to any sprint that has been started.
It is also worth mentioning that this query does not show issues that are assigned to future sprints (there is a clear distinction between sprints that have been started compared to them which has not been started yet).
After the defined period has passed it is likely a sprint will be closed. For historical searches and analysis you will likely be interested in a reporting of issues that are assigned to closed sprints.
The query is similar to the ones you are already familiar with. You can query for issues in closed sprints like the following:
sprint in closedSprints()
Hint: issues can be part of several sprints - one example are issues that are 'rolling over' to the next sprint because they could not be finished in the previous sprint.
Therefore it can be perfectly possible that you are seeing an issue as a result of both queries "sprint in closedSprints()" and "sprint in openSprints()".
From the issue view you will recognize that by looking at the "Sprint" field.
In the example above you see an open sprint listed, alongside with one completed sprint.
You can also see which issues are contained in sprints at all. This is recorded in the issue's respective field called "Sprint".
The query is easy again:
project = "UHD" AND Sprint is not EMPTY
I hope this showed you how easy queries for sprints work in Jira Cloud.
In case you are interested in using Scrum for your team there is awesome documentation from Atlassian available from "Agile Coach":
Agile Coach is a useful guide for learning more about Agile methodologies, no matter if you have just started your journey or if you an experienced practitioner looking to just verify some detailed information.
383 accepted answers