Sprints appearing on multiple boards in Jira Data Center, Server, or Cloud
Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
A sprint may show on multiple boards, including one in which it wasn't created. Also, modifying a sprint will affect a sprint on another board. Examples include:
- A sprint shows on a board in which it wasn't created.
- Making a change to a sprint on one board affects a sprint on another board.
- A sprint shows on a board after an issue from another board has been moved to the sprint.
- Attempting to close a sprint in one board requires the Manage Sprints permission to be granted from projects that are associated with another board.
Confirm whether there are multiple sprints
- Verify if the sprints are indeed two different entities by checking the sprint IDs.
- Use the Issue Navigator to search for issues in each sprint. If any of the sprints contain issues from more than one board, the sprint will display on all of the boards.
Fix sprints appearing on more than one board by mistake
- Identify the sprints that are incorrectly included in a board.
- If one sprint is used where there should be two, create a new sprint in the board that is missing one.
- Move issues to relevant sprints by editing their Sprint field value. Do the same to remove them from sprints that should only be displayed in those issues' boards.
Alternatively you can also choose to delete a sprint.
What causes sprints to appear on more than one board at a time
Sprints aren't dependent on a specific board or project. It's therefore possible for a sprint to be displayed in more than one board. It is still one entity though, and changes made to it in one board will be reflected in the other too.
It can happen that the same sprint is used in two boards by mistake. For example, if the sprint naming convention is the same for all boards, and the incorrect sprint with the same name is linked to an issue.
Furthermore, if an issue was modified or moved, and as a result is displayed in a new board, the sprints that it was originally assigned to will be shown in that new board too. In such cases, it would be unexpected that the same sprint is displayed on two boards, even though it is technically correct.
A sprint will be displayed on a board under one of the following conditions:
- The sprint was created while viewing that board.
- For users on Jira Cloud, this can be checked with the Jira REST API Sprint endpoint. The "originBoardId" key will contain the ID of the board where the sprint was originally created.
- For users on Jira Server or Data Center, this can be checked in the database. The RAPID_VIEW_ID column in the "AO_60DB71_SPRINT" table will contain the origin board ID.
- A board referencing the sprint was copied. When this happens, the references to the sprint are copied as well.
- Issues included in the board's JQL filter are associated with the sprint.
Additional Information
It is recommended that your team includes the project or intended board name when you name your sprints, in order to avoid confusion.
We've also identified that in some cases in Jira Server or Data Center, a sprint appears in multiple boards in the REST API, but not in the UI. This issue is tracked in JSWSERVER-21236 - Sprint appears in REST API but not in UI when only subtask matches board filter.
This can affect features or apps that depend on this, like ScriptRunner's nextSprint() JQL function.