#Xboard stories software

We can verify this by enabling some additional logging and then seeing exactly what JQL JIRA Software is using to return issues.

If results are returned, however,В they are not returned through the board, it may be to do with additional causes.

Try accessing the filter directly that is used for the board ( Tools > Configure > Filter > Click on the Saved Filter).

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

If using the Script Runner plugin, verify the behavior as documented in GRV-232.

Make sure there are no Issue Types or Statuses that are integers, as this is a known bug tracked under.

Verify the user has access to those issues with the JIRA Admin Helper plugin.

See JIRA Software Kanban board does not show all Issues.

Make sure the sprint custom field is not hidden in the Field Configurations page - Specifying field behavior.

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.

Make sure there are no issues blocked by the board's filter - Configuring filters.

Modify the board's filter to use the new project name or key - Configuring filters.Please refer to Configuring columns for more information. Make sure your board has multiple columns populated, JIRA Software will consider the last column that's filled in as the end column.Map the columns in board's configuration to the correct status, please refer to Configuring columns for more information.Refer Configuring a custom field for more information. Set the Sprint's custom field Search Template to JIRA Agile Sprint Field Searcher.Set the Sprint's custom field contexts to 'Global' or to the projects to be used in JIRA Software.Make sure that JIRA Software is re-indexed (Full Reindex) - Search indexing.If on Active SprintВ section and no issues on currently running sprints, the board will be empty, but issues will still be listed on the backlog.The Fast Transition functionality in the Script Runner plugin may be causing problems.There are Issue Types or Statuses that use integers (1, 2, 3 and so on).The user does not have the appropriate permissions to view or edit those issues.'Fix version' is set to 'Hide' in 'Field Configurations' page.The sprint custom field is hiddenВ through Field Configurations.

Keep in mind that the board's filter controls visibility of the issues everywhere in the board, including all Agile reports. The board's filter is blocking some issues.Only the first column is populated with statuses.Mapped columns to statuses are not mapped in the board's configuration.The Search Template for SprintВ custom fieldВ is not set to JIRA Agile Sprint Field Searcher.The context of the Sprint custom fieldВ is not set to global.

JIRA Software hasn't reindexed properly.Issues are not appearing in the Plan or Work boards for either Scrum or Kanban, or reports visible within those boards. This article only applies to Atlassian products on the server and data center platforms. Platform Notice: Server and Data Center Only.

Xboard stories