Internal Server Error is thrown when accessing GreenHopper Scrum Board
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
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:
1
2
3
4
5
6
7
8
9
10
11
12
13
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)Solution
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
Was this helpful?