Sprint field is returning blank results via Create or Edit issue screen

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

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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

User is unable to see the active sprint auto-suggested in the Sprint field via the Create or Edit issue screen:

Environment

Jira 9.4.1

Diagnosis

  1. You have checked theproject settings including users & roles , permission scheme, and issue security scheme:

    • Browse Projects

    • Manage Sprints

    • Start/Complete Sprints

    • No issue security scheme configured in the project.

  2. You have checked theboard filter permission it is accessible by the user.

  3. You have checked the users can search for the issues with the JQL query:

    1 Sprints="missing_sprint_name"
  4. You have checked the missing Sprint is linked to the Board A.

  5. You have "Relevant sprints" checked via Jira Software Configuration.

  6. You have checked user can access Board A and manage the sprints. If not, please check the KB to fix the issue -> Some users can't manage a Sprint (create, start, edit, complete, move) due to incorrect project permissions

  7. Run the following SQL query to look for the Origin board: 

    1 2 3 4 5 6 7 8 9 10 11 select b."ID" as board_id, b."NAME" as board_name, sr.id as filter_id, sr.filtername as filter_name, sr.reqcontent, s."ID" as sprint_id , s."NAME" as sprint_Name from "AO_60DB71_SPRINT" s join "AO_60DB71_RAPIDVIEW" b on s."RAPID_VIEW_ID" = b."ID" join searchrequest sr on b."SAVED_FILTER_ID" = sr.id where s."NAME" = '<SprintName>';

    From the results, you can see the sprint origin board is not belong to the 'Board A' but instead 'Board B

Cause

The reason is that you have Sprints appearing on multiple boards in Jira server as quoted:

"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 erroneously, e.g. if the sprint naming convention is the same for all boards, and the incorrect sprint with the same name was 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 in two boards, even though it is technically correct."

Solution

  1. Re-check again the diagnosis step on the origin board such as 'Board B'

  2. Ensure the user can access Board B. If not, please follow How to remove Visibility restrictions on a board solution.

Updated on March 12, 2025

Still need help?

The Atlassian Community is here for you.