|Jira Agile 6.3
Issues are not appearing in the Plan or Work boards for either Scrum or Kanban.
|JIRA is not reindexed after JIRA Agile installation.|
Make sure that JIRA is re-indexed (Full Reindex) after the installation of JIRA Agile plugin - Search Indexing.
The context of the Sprint custom field is not set to global.
Set the Sprint's custom field contexts to 'Global' or to the projects to be used in JIRA Agile. Refer Configuring a Custom Field for more information.
The Search Template for Sprint custom field is not set to JIRA Agile Sprint Field Searcher.
Set the Sprint's custom field Search Template to JIRA Agile Sprint Field Searcher. Refer Configuring Search Template for more information.
Mapped columns to JIRA Status are not mapped in the board's configuration.
Map the columns in board's configuration to the correct JIRA Status, please refer to Configuring Columns for more information.
|The JIRA project has been renamed.||Modify the board's filter to use the new project name or key - Configuring Filters.|
The board's filter is blocking some issues.
Make sure there are no issues blocked by the board's filter - Configuring Filters.
The sprint custom field is hidden through Field Configurations.
Make sure the sprint custom field is not hidden in the Field Configurations page - Specifying Field Behavior.
|'Fix version' is set to 'Hide' in 'Field Configurations' page.||See Planning and Task Board Cards are not Visible when 'Fix Version' Field is Hidden|
The user does not have the appropriate permissions to view or edit those issues.
Verify the user has access to those issues with the JIRA Admin Helper plugin.
There are Issue Types or Statuses in JIRA that use integers (1, 2, 3 and so on).
The Fast Transition functionality in the Script Runner plugin may be causing problems. This is a bug as tracked under GRV-232.
If using the Script Runner plugin, verify the behaviour as documented in GRV-232.
The following troubleshooting steps will also be helpful if the above does not resolve the problem:
DEBUGin Logging and Profiling.
Reload the board. This will give you the JQL in the logs that JIRA Agile is using in the logs, e.g.:
Take that JQL and run it directly against the Issue Navigator. For example:
cf is the Sprint field in this example.