Sprints Missing on Scrum Board in Jira Cloud

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

Check if your sprint has started and confirm the JQL filters on your board compared with work items included in that sprint. These factors are the most important in determining whether a sprint appears on a board.

Solution

What determines if a sprint appears on a board?

A Sprint must meet at least one of these conditions to appear on a Scrum board

The Sprint was created from that board (the board is the origin board)

The Sprint contains work items that match the board's filter

* The Sprint always appears on its origin board, whether it has started or not, and regardless of its work items.

* To determine the origin board of a given sprint, you can query the API endpoint:

https://<your-domain>.atlassian.net/rest/agile/1.0/sprint/{sprintId}

* If the sprint hasn't started, it appears because at least one work item matches the board's JQL filter and isn't in the Done column.

* If the sprint has been started but not completed, work items in the Done column will also cause the sprint to appear on the board.

After you complete a sprint, it will no longer appear in Active Sprints or Backlog, but it will still appear in the Sprint Reports section.

Why is my sprint not appearing on the board where I want to see it?

Based on the qualifications above, we can determine why a sprint fails to appear where it is expected to.

The sprint has not started, and the board is not the origin board of the sprint

  • If the board is not the origin board and there are no work items in the sprint that match the JQL filter on the board, the sprint won't appear there.

  • If a work item does match the board JQL and is in the sprint, it may be in a status that is mapped to the rightmost Done column of the board.

  • Work Items in this state won't cause a non-started sprint to appear on this board, so you can change their status or the board column mapping if necessary.

The sprint has already been completed

Sprints that are complete won't appear in Active Sprints or Backlog view for a Jira board. The only place you'll see completed sprints listed is within the Sprint Reports section.

Demonstration of sprints displayed on various boards

Assume that a project exists with key TEST. This project includes a board called SCRUM, where you create a sprint called Sprint for testing. The sprint hasn't started, and no work items have been added to it. Since SCRUM is the origin board, the Sprint appears on that board.

Copy the SCRUM board and name the copy COPYSCRUM. COPYSCRUM shares the same filter and column configuration as SCRUM, but the Sprint is not appearing because COPYSCRUM is not the sprint's origin board. Since there are no work items in the sprint, even though SCRUM and COPYSCRUM have the same filter, no work items in the board filter match this sprint.

No work items created yet:

SCRUM

COPYSCRUM

Backlog View

Sprint for testing

(no sprints)

Active Sprints view

(no sprints)

(no sprints)

Now add a new work item to the sprint that meets the board filter requirement (the JQL filter is simply "project = TEST"). The Sprint will show in the board COPYSCRUM since this work item can be found by the board filter and is in a status that is not mapped to the rightmost Done column of the board.

After creating work item TEST-1:

SCRUM

COPYSCRUM

Backlog View

Sprint for testing

Sprint for testing

Active Sprints view

(no sprints)

(no sprints)

If the work item status changes to Closed, the Sprint will no longer appear on the COPYSCRUM board. That's because the Closed status is mapped to the rightmost column on this board.

Once you start the sprint, it will appear on the Active Sprints view for both of our boards until the sprint is completed.

With TEST-1 in the status To Do and the sprint started:

SCRUM

COPYSCRUM

Backlog View

Sprint for testing

Sprint for testing

Active Sprints view

Sprint for testing

Sprint for testing

Updated on April 30, 2025

Still need help?

The Atlassian Community is here for you.