Child pages
  • Internal Server Error is thrown when accessing GreenHopper Scrum Board
Skip to end of metadata
Go to start of metadata

Problem

When accessing a GreenHopper board, instead of getting the board it returns an Internal Server Error, as per illustrated below:
 

 

 

The following appears in the atlassian-jira.log:

2012-12-22 16:55:46,818 http-bio-8070-exec-21 ERROR twilsmann 1015x563x1 11qr25v 25.69.75.93 /rest/greenhopper/1.0/xboard/config.json [greenhopper.web.rapid.RapidBoardResource] Unable to complete GreenHopper REST method 
java.lang.NullPointerException
	at com.atlassian.greenhopper.service.issuelink.EpicCustomFieldServiceImpl.getDoneEpicStatusOption(EpicCustomFieldServiceImpl.java:139)
	at com.atlassian.greenhopper.web.rapid.RapidBoardViewModelFactory.getEpicConfig(RapidBoardViewModelFactory.java:296)

[.....]
2012-12-22 16:55:46,855 http-bio-8070-exec-21 ERROR twilsmann 1015x563x1 11qr25v 25.69.75.93 /rest/greenhopper/1.0/xboard/config.json [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service
java.lang.NullPointerException
	at com.atlassian.greenhopper.service.issuelink.EpicCustomFieldServiceImpl.getDoneEpicStatusOption(EpicCustomFieldServiceImpl.java:139)
	at com.atlassian.greenhopper.web.rapid.RapidBoardViewModelFactory.getEpicConfig(RapidBoardViewModelFactory.java:296)
	at com.atlassian.greenhopper.web.rapid.RapidBoardViewModelFactory.buildRapidGlobalConfig(RapidBoardViewModelFactory.java:179)
	at com.atlassian.greenhopper.web.rapid.RapidBoardViewModelFactory.getRapidViewConfigModel(RapidBoardViewModelFactory.java:166)
	at com.atlassian.greenhopper.web.rapid.RapidBoardResource$2.call(RapidBoardResource.java:83)

Diagnosis

The problem may occur because some of GreenHopper custom fields do not have any Configuration Context configured. Please refer to the screenshot below:

Diagnostic steps

  • In our case here, we can see that the Epic Colour, Epic Name, Epic Status and Story Points field are missing their configuration context. 

Resolution

  • In order to fix the problem, we need to recreate the fields default configuration context
  • Go to Administration > Custom Fields, and add the configuration context for all of the affected fields

Help us improve!
  • No labels

3 Comments

  1. Initially, JIRA had exceeded the file open limit and we had to restart JIRA.  One of the users had started the Start Sprint process at the same time that we were re-starting JIRA.  After JIRA came back up, when opening the scrum board for the project that did not complete the Start Sprint process, we were experiencing the exact same symptom: Internal Server Error.  We re-indexed the project, and the users were then able to access the scrum board.

    1. Brian Cummings, thanks. That's exactly the issue we had and re-indexing resolved it.

      Perhaps its worth to add it to the KB discussing file open limit issue

  2. Newer versions of GreenHopper don't let you configure the context for a GH field I think