Issues are not appearing in Boards, including Agile reports

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.


Issues are not appearing in the Plan, Scrum and Kanban Boards or reports visible within those boards. 


  1. The affected issues were not reindexed.
  2. You have a quick filter enabled.
  3. The context of the Sprint custom field is not set to global.
  4. The Search Template for Sprint custom field is not set to JIRA Software Sprint Field Searcher.
  5. Mapped columns to statuses are not mapped in the board's configuration.
  6. Only the first column is populated with statuses.
  7. The project has been renamed and filter still uses old name.
  8. The board's filter is blocking some issues. Keep in mind that the board's filter controls visibility of the issues everywhere in the board, including all Agile reports. 
  9. The sprint custom field is hidden through Field Configurations.
  10. 'Fix version' is set to 'Hide' in 'Field Configurations' page.
  11. The user does not have the appropriate permissions to view or edit those issues.
  12. There are Issue Types or Statuses that use integers (1, 2, 3 and so on).
  13. On a Scrum Board, Active Sprint section is empty, but issues will still be listed on the backlog.
  14. Sub-Filters may hide issues.
  15. On a Kanban board, Epics Panel is enabled which will move all Epics to the backlog.
  16. On a Kanban board, Swimlanes is enabled.


  1. Make sure that JIRA Software is re-indexed (Full Reindex) - Search indexing.
  2. Disable the quick filter. Refer to Configuring Quick Filters for more information.
  3. Set the Sprint's custom field contexts to 'Global' or to the projects to be used in JIRA Software. Refer to Configuring a custom field for more information.
  4. Set the Sprint's custom field Search Template to JIRA Software Sprint Field Searcher. Refer to Configuring a custom field for more information.
  5. Map the columns in board's configuration to the correct status, please refer to Configuring columns for more information.
  6. Make sure your board has multiple columns populated, JIRA Software will consider the last column that's filled in as the end column. Please refer to Configuring columns for more information.
  7. Modify the board's filter to use the new project name or key - Configuring filters.
  8. Make sure there are no issues blocked by the board's filter - Configuring filters. If the board filter retrieves issues based on an additional field like customfield or label, ensure that each of the issues that should be shown in the board and their Epics has the correct customfield or label value.
  9. Make sure the sprint custom field is not hidden in the Field Configurations page - Specifying field behavior.
  10. See Jira Software Kanban board does not show all issues.
  11. Verify the user has access to those issues with the JIRA Admin Helper plugin or by accessing the issue directly.
  12. Make sure there are no Issue Types or Statuses that are integers, as this is a known bug tracked under JRASERVER-31898 - Getting issue details... STATUS .
  13. Add issues to active sprints by editing the issue directly or by dragging it to the active Sprint in the backlog.
  14. See Jira Software Kanban board does not show all issues and Configuring filters.
  15. Please refer to Configuring columns - Kanban Backlog and disable the Epics Panel.
  16. Swimlanes may filter issues such as Epics if you have Base Swimlanes on Epics selected. See Configuring Swimlanes to disable it.

Additional Troubleshooting

The following troubleshooting steps will also be helpful if the above does not resolve the problem:

  1. Try accessing the filter directly that is used for the board (Tools > Configure > Filter > Click on the Saved Filter).
  2. If results are returned, however, they are not returned through the board, it may be to do with additional causes. We can verify this by enabling some additional logging and then seeing exactly what JQL JIRA Software is using to return issues.
  3. Enable the extra JQL logging by setting to DEBUG in Logging and Profiling.
  4. Reload the board. This will give you the JQL in the logs that JIRA Software is using in the logs, e.g.:

    2013-03-01 15:48:35,607 http-8910-9 INFO allyourbase 948x1325x2 5a6eo1 /rest/JIRA Agile/1.0/xboard/work/allData.json [] JQL query: {issuekey = "CDSSF-442"} AND {status in ("3", "1", "6", "5", "4", "10022", "10020")} AND {cf[10370] in openSprints()} order by Rank ASC
  5. Take that JQL and run it directly against the Issue Navigator. For example:

    issuekey = CDSSF-442 AND status in ("3", "1", "6", "5", "4", "10022", "10020") AND cf[10370] in openSprints() order by Rank ASC

    cf[10370] is the Sprint field in this example.

  6. This can help identify any problems with that JQL where the error may not be reflected in the board. If the Sprint field is hidden on the Field Configuration you may face the problem described on this article:
    1. The Jira search page shows the error "XXXX does not exist or you do not have permission to view it"
    2. If that's your case, follow the steps on that page to resolve it.

Issues are not appearing in the Plan or Work boards for either Scrum or Kanban.

Last modified on Jan 26, 2023

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.