JQL Active Sprint Guide: Query Active Sprints in Jira

As a project manager, you can’t help but know the sheer scale of having to line up tasks, deadlines, and team priorities all at the same time during a given sprint. If there is the slightest error in performing a task, then this will naturally result in delays and missed deadlines.

So, how do you make sure no details are being overlooked? 

By using the active sprint view in Jira. 

The JQL active sprints help you view your team’s progress, monitor tasks, identify blockers, and keep your agile team up-to-date with issues, bugs, and any changes that arise within the sprint.

To help you with this, here’s our guide to Jira’s active sprint functionality. We have discussed in detail how you can query and analyze these active sprints in the best way so you can focus on the most relevant aspects. 

Understanding JQL Syntax for Active Sprints

JQL (Jira Query Language) helps you unpack advanced functionality in Jira, allowing you to make customized queries to filter, sort, and extra data as per your needs and requirements. This flexibility makes the JQL a critical aspect of making informed decisions with regard to projects. 

While Jira’s default interface offers a broad overview, JQL allows you to go deep into these active sprints and helps you view data like blockers, task assignments, and dependencies. It also gives you the control to filter, sort, and analyze specific elements of the respective active sprint. 

Whether it’s tracking blockers, assigning tasks to different teams, dependencies, or even tracking bugs before an upcoming release, viewing the active sprints will help you decide better. 

Here are some of the JQL syntaxes that you can use for active sprints ranging from basic to advanced to get started within Jira:

1. JQL Query For Active Sprints

If you want to see all the active sprints, then use the opensprints() function. This function will showcase all the ongoing sprints and tasks that are undone to you. 

If you have a project, and it is assigned, then this function can be customed as:

project = “Your Project Name/ID” AND status = “To Do” AND Sprint in openSprints()

2. If You Have Any Blocked Issues

These are the issues or like tasks that are stuck or require immediate attention.

status = “Blocked” AND sprint in openSprints()  

3. Tracking High-Priority Issues

If you want to view tasks that focus on critical or high-priority tasks, that should be resolved first.

priority = “High” AND sprint in openSprints() 

4. Detecting Scope Creep

If you want to monitor issues that are specifically added after the sprint began using advanced JQL functions, then you can use this syntax. Note: This action requires plugins like ScriptRunner.

issueFunction in addedAfterSprintStart(“BoardName”, “SprintName”)  

5. Sorting Results

If you want to organize your query output for better readability or prioritization, then filter it out using this syntax. 

sprint in openSprints() ORDER BY priority DESC  

6. Tracking Dependencies

If you have dependencies on other teams and want to identify tasks linked to or dependent on others within the sprint, then use this sprint. 

linkedIssues = “ISSUE-123” AND sprint in openSprints() 

These are some basic to advanced JQL query syntaxes that you can use. Also, in the next section, we will take you through a step-by-step procedure to view active sprints in Jira. 

Step-by-Step Guide: How to Query Active Sprints Using JQL

Querying active sprints using JQL in Jira can be a game-changer for managing and monitoring your Agile workflows. Here’s a step-by-step guide to help you leverage JQL effectively:

Step 1: Create a JQL Filter

1. Access the Advanced Search:

• Log in to Jira and navigate to the Filters dropdown in the top menu.
• Select Advanced Issue Search to access the JQL input bar.

2. Input the Query:
   • In the search bar, enter the following JQL query to fetch all issues in active sprints:
     sprint in openSprints() ORDER BY Rank 

Here, “Order by” is a condition; you can use other conditions as well, like Order by Priority, “Order by due date,” or “Order by status”(e.g., To do, In progress, Done). If you want to enlist the active sprints in a specific project then you can select the “Project name” in the filter option itself.

3. Save the Filter:
   • Once the results are displayed, click on the Save As button at the top-right corner of the search interface.
   • Name something meaningful for the filter, such as “Open Sprints Issues.”
   • Add a description for clarity and save it.

Step 2: Create a New Board Using the Filter

1. Navigate to Create a New Board:
   • Go to the Jira sidebar and click on the Boards dropdown menu.
   • Select “Create Board” and choose the type of board (Scrum or Kanban) based on your project needs.
2. Select a Filter for the Board:
   • When prompted, select the option to “Create a board with an existing filter.”
   • Choose the saved filter “Open Sprints Issues” from Step 1.
3. Name the Board:
   • Provide a name for your board, such as “Active Sprint Overview.”
   • Assign the board to a project and save.

Step 3: View Open Sprints in the Backlog

1. Access the New Board:
   • Navigate to the newly created board from the Boards dropdown menu.
2. Switch to Backlog View:
   • Open the board and select the Backlog tab from the menu.
   • The Backlog view will display a list of all open sprints and their associated issues.
3. Understand the Display:
   • The Backlog view separates issues by sprint, making it easier to see each sprint individually.
   • Note: The Active Sprints view merges all issues into a single sprint, which can be less helpful for this purpose.

Best Practices for Managing Active Sprints with JQL

Even though writing JQL queries may seem interesting and helpful while managing a software development project and a team, it’s equally important to manage these active sprints. 

You can do this by following the below-mentioned easy steps:

Update Jira Filters Regularly

Jira’s filtering system can help you track issues and project flow. However, it’s highly recommended that filters be reviewed and updated to make sure they stay relevant as the project evolves.  

Use the RemovedAfterSprintStart Function

Use this function to show issues that were removed from a board after a sprint started, and this way, you can keep your active sprint space clean and clear.

Use Jira’s Capacity Planning Tools

It’s always better to allocate resources across sprints to ensure that each team member’s workload is balanced and given to them at the right time. Avoid sparing or keeping things, especially allocation of work, till the last minute. 

Use Jira’s Prioritization And Filter Feature Regularly

It is always better to rank tasks and make sure that the high-priority items are being addressed first. Also, using filters like “status changed from () to ()” or “status WAS IN ()” is better to track issues and project flow.

Use Jira’s Linking Features

Also, it’s very important to start identifying and managing dependencies between tasks in different sprints to avoid delays in projects. So, it’s best to use Jira’s linking feature beforehand to make sure the other team has also kept the respective tasks in priority rather than in the parking lot. 

Maintain Focus And Boost Team Morale

Clearly define and communicate the goals of each sprint to your team members and keep them prepared for the work. It’s also very important to recognize and celebrate achievements to motivate them to deliver in the same manner for the next sprints. 

FAQs