Child pages
  • JIRA Agile upgrade to 6.2.2 fails
Skip to end of metadata
Go to start of metadata


JIRA Agile upgrade to 6.2.2 fails.

The following appears in the atlassian-jira.log:

2013-05-29 08:34:41,828 pool-13-thread-2 ERROR rweidmann 506x35861x1 2mw5j9 /rest/plugins/1.0/ [sal.core.upgrade.PluginUpgrader] Upgrade failed: null
	at com.atlassian.greenhopper.customfield.CustomFieldServiceImpl.associateWithDefaultScreen(
	at com.atlassian.greenhopper.upgrade.GhUpgradeTask034.performUpgrade(
	at com.atlassian.greenhopper.upgrade.AbstractGhUpgradeTask.doUpgrade(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(  <+1> (
	at java.lang.reflect.Method.invoke(
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(


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.


  1. If the diagnostic query returns NO RESULTS:
    1. Add a screen in the Admin ui. Name it "Default Screen" and add some tabs to it.
    2. Shut down JIRA
    3. Take a database backup.
    4. Change the id value for the Default Screen in your db
    5. Update your id to be 1:

      update fieldscreen set id = 1 where name = 'Default Screen'
    6. Fix your tabs to be associated correctly: 

      update fieldscreentab set fieldscreen = 1 where fieldscreen not in (select id from fieldscreen);
    7. Start JIRA back up and make sure everything works.
  2. If the diagnostic query returns a result
    1. Go into the JIRA admin UI
    2. Rename the Screen which the query returned to be "Default Screen"
    3. Disable the JIRA Agile add-on, then re-enable it and verify everything is working

Related Content

Bug for this is at:  GHS-9043 - Getting issue details... STATUS


Help us improve!