Unable to access Planning mode due to at com.atlassian.greenhopper.service.rapid.RapidViewClauseServiceImpl.getPlanModeClause
Symptoms
When accessing the Plan Mode in Rapid Board. You will see a red error message "Internal Server Error" and no Plan Mode information will be displayed.
In the console and server logs you will find this stack trace:
2012-10-26 10:35:46,909 http-8080-1 ERROR jira 635x463x1 127uqc0 xxx.xxx.xxx.xxx,xxx.xxx.xxx.xxx /rest/greenhopper/1.0/xboard/plan/backlog/data.json [server.impl.application.WebApplicationImpl] Internal server error
java.lang.NullPointerException
at com.atlassian.greenhopper.service.rapid.RapidViewClauseServiceImpl.getPlanModeClause(RapidViewClauseServiceImpl.java:134)
at com.atlassian.greenhopper.service.rapid.RapidViewClauseServiceImpl.getClauseForBuilder(RapidViewClauseServiceImpl.java:70)
at com.atlassian.greenhopper.service.rapid.RapidViewQueryServiceImpl.getBacklogQuery(RapidViewQueryServiceImpl.java:189)
at com.atlassian.greenhopper.service.rapid.RapidViewQueryServiceImpl.getBacklogQuery(RapidViewQueryServiceImpl.java:167)
at com.atlassian.greenhopper.web.rapid.list.RapidIssueEntryQueryServiceImpl.collectBacklogIssues(RapidIssueEntryQueryServiceImpl.java:164)
at com.atlassian.greenhopper.web.rapid.plan.PlanningModeResource.loadBacklogData(PlanningModeResource.java:208)
at com.atlassian.greenhopper.web.rapid.plan.PlanningModeResource.access$300(PlanningModeResource.java:53)
at com.atlassian.greenhopper.web.rapid.plan.PlanningModeResource$1.call(PlanningModeResource.java:118)
at com.atlassian.greenhopper.web.rapid.plan.PlanningModeResource$1.call(PlanningModeResource.java:103)
at com.atlassian.greenhopper.web.util.RestCall.response(RestCall.java:48)
at com.atlassian.greenhopper.web.AbstractResource.response(AbstractResource.java:48)
at com.atlassian.greenhopper.web.rapid.plan.PlanningModeResource.getBacklogData(PlanningModeResource.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
...
Cause
The original Epic issue type is deleted, this is a Bug in JIRA Agile 6.0.6 - - GHS-6495Getting issue details... STATUS
Resolution
Backup
The following changes require direct database modification. Please ensure that the JIRA database backup is taken before proceeding to the resolution steps. It is also recommended that JIRA is taken out of service before starting the database backup.
- Go to Administration > Issue Type > Click on Edit for Epic issue type
Note the ID of the Epic issue type on the address bar, in this example the Epic id is 7 : - Shut down JIRA
Run the below SQL in the JIRA database to locate the current configuration data:
select id, propertyvalue from propertytext where id = (select id from propertyentry where property_key ='SCRUM_DEFAULT_TEMPLATE_CONFIGURATION');
The returned text will be a long one and we recommend copying the contents from the displayed output to a text editor of your choice.
Modify the XML output got in the previous step (using the text editor) to so that the below entries refer to the correct Epic issue type ID
... <entry> <string>gh.issue.epic</string> <string>9</string> </entry> ...
Fix the ID to match with the Epic issue type ID from the UI.
... <entry> <string>gh.issue.epic</string> <string>7</string> </entry> ...
Update the
propertytext
table using the following SQLupdate propertytext set propertyvalue = 'copy the contents from the text editor containing the xml here' where id = (select id from propertyentry where property_key ='SCRUM_DEFAULT_TEMPLATE_CONFIGURATION');
- Restart JIRA