Child pages
  • Issues are not appearing in JIRA Agile Rapid Boards
Skip to end of metadata
Go to start of metadata

Symptoms

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

Causes and Resolution

CauseResolution
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).

Make sure that JIRA does not have any Issue Types or Statuses that are integers, as this is a known bug tracked under  JRA-31898 - Getting issue details... STATUS

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.

Additional Troubleshooting

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

  1. Try accessing the JIRA 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 JIRA Agile 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 Agile is using to return issues.
  3. Enable the extra JQL logging by setting com.atlassian.jira.issue.search.providers to DEBUG in Logging and Profiling.
  4. Reload the board. This will give you the JQL in the logs that JIRA Agile is using in the logs, e.g.:

    2013-03-01 15:48:35,607 http-8910-9 INFO allyourbase 948x1325x2 5a6eo1 172.22.2.187 /rest/JIRA Agile/1.0/xboard/work/allData.json [issue.search.providers.LuceneSearchProvider] 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

    (info) 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 JIRA Agile board. In this particular example, the Sprint field was hidden on the Field Configuration and the below error presented in the Issue Navigator, but not JIRA Agile:
  7. Fix the problem with the field configuration and test the board again.
Help us improve!

 


 

2 Comments

  1. Page is currently not loading. Content is replaced with this text:

     

    Unable to render {include} The included page could not be found.

    1. Thanks for the heads-up. I think the problem should be resolved now, but let us know if you still have trouble viewing the article.