-
Bug
-
Resolution: Fixed
-
High (View bug fix roadmap)
-
6.2.2
-
None
-
6.02
-
Error in the logs:
2013-05-29 08:34:41,828 pool-13-thread-2 ERROR rweidmann 506x35861x1 2mw5j9 10.3.4.157 /rest/plugins/1.0/ [sal.core.upgrade.PluginUpgrader] Upgrade failed: null java.lang.NullPointerException at com.atlassian.greenhopper.customfield.CustomFieldServiceImpl.associateWithDefaultScreen(CustomFieldServiceImpl.java:285) at com.atlassian.greenhopper.upgrade.GhUpgradeTask034.performUpgrade(GhUpgradeTask034.java:50) at com.atlassian.greenhopper.upgrade.AbstractGhUpgradeTask.doUpgrade(AbstractGhUpgradeTask.java:62) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) <+1> (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307) at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:58) at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:62) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
Then we look at: https://bitbucket.org/greenhopper/greenhopper/src/b9905ec7f01728c684e930ea544068bc149b8039/greenhopper/src/main/java/com/atlassian/greenhopper/customfield/CustomFieldServiceImpl.java?at=default and find that we are looking for DEFAULT_SCREEN_ID from com.atlassian.jira.issue.fields.screen.FieldScreen. When we look there, we find that this is defined as id=1.
Investigating the user's DB will find that this does not exist or is not named "Default Screen".
Workaround:
If it is not named "default screen", and is named just "default", it was likely upgraded from JIRA 3.x. Just rename it to Default Screen and then disable, and re-enable GreenHopper.
If it does not exist, then make a backup. Then make a new screen must be made via the UI (and add some tabs to it). Then the id in the fieldscreen table must be updated to be 1. Then the fieldscreentab table must also be updated:
update fieldscreentab set fieldscreen = 1 where fieldscreen not in (select id from fieldscreen);
Then restart JIRA.
KB at: https://confluence.atlassian.com/display/GHKB/GreenHopper+upgrade+to+6.2.2+fails
[JSWSERVER-9043] GreenHopper upgrade to 6.2.2 fails
on shipit
We add the epic link field to all view operation screens, and the default one is one of them.
We had problems with the 6.2.2 update. Then tried 6.2.3 and fixed 'Default Screen'. The fieldscreentab query did not return any results.
We ran the update again and after the successful installation process, there is a message saying that some update tasks did not complete.
The Greenhopper log shows two errors:
*********************************************************************************
Atlassian GreenHopper v6.2.3 #d29c4d5d99fd built 2013-06-12T21:02:12.357-05:00 - plugin started. Get Agile!
*********************************************************************************
2013-06-20 09:09:44,901 http-bio-8081-exec-22 WARN bcoleman 549x1256x1 1upwjmd 10.3.51.72 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [manager.issue.fields.ManagedFieldConfigurationRestorerImpl] Too many configuration schemes for 'Epic Status' field
2013-06-20 09:09:45,515 http-bio-8081-exec-22 INFO bcoleman 549x1256x1 1upwjmd 10.3.51.72 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [com.atlassian.greenhopper.upgrade] =========================================
2013-06-20 09:09:45,515 http-bio-8081-exec-22 INFO bcoleman 549x1256x1 1upwjmd 10.3.51.72 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [com.atlassian.greenhopper.upgrade] Starting upgrade task (buildNumber=31) : Remove hard-coded issue details fields
Any thoughts?