JIRA Agile upgrade to 6.2.2 fails
症状
JIRA Agile upgrade to 6.2.2 fails.
atlassian-jira.log
に次のメッセージが表示される。
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)
診断
Run the query:
select name from fieldscreen where id = 1;
If there are no results then you need to use resolution 1 below.
If there is a result you need to use resolution 2 below.
原因
JIRA Agile is trying to update the default screen which may not exist on some JIRA instances.
ソリューション
- If the diagnostic query returns NO RESULTS:
- Add a screen in the Admin ui. Name it "Default Screen" and add some tabs to it.
- Jira を終了します。
- Take a database backup.
- Change the id value for the Default Screen in your db
Update your id to be 1:
update fieldscreen set id = 1 where name = 'Default Screen'
Fix your tabs to be associated correctly:
update fieldscreentab set fieldscreen = 1 where fieldscreen not in (select id from fieldscreen);
- Start JIRA back up and make sure everything works.
- If the diagnostic query returns a result
- Go into the JIRA admin UI
- Rename the Screen which the query returned to be "Default Screen"
- Disable the JIRA Agile add-on, then re-enable it and verify everything is working
関連コンテンツ
Bug for this is at: - GHS-9043Getting issue details... STATUS
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.