Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9887

Upgrade to 6.3.2.1 fails with a NullPointerException in the logs

    XMLWordPrintable

Details

    Description

      Symptoms

      @4000000052497be016a77234 2013-09-30 06:25:42,378 TP-Processor12 ERROR sysadmin 385x976x1 1dm2fuh 59.167.133.100,131.103.27.4 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [sal.core.upgrade.PluginUpgrader] Upgrade failed: null
      @4000000052497be016a77dec java.lang.NullPointerException
      @4000000052497be016a77dec       at com.atlassian.greenhopper.upgrade.GhUpgradeTask040.findAndUpdateOptions(GhUpgradeTask040.java:190)
      @4000000052497be016a781d4       at com.atlassian.greenhopper.upgrade.GhUpgradeTask040.updateEpicStatusOptions(GhUpgradeTask040.java:162)
      @4000000052497be016a8a6cc       at com.atlassian.greenhopper.upgrade.GhUpgradeTask040.performUpgrade(GhUpgradeTask040.java:93)
      @4000000052497be016a8aab4       at com.atlassian.greenhopper.upgrade.AbstractGhUpgradeTask.doUpgrade(AbstractGhUpgradeTask.java:62)
      @4000000052497be016a8aab4       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      @4000000052497be016a8ae9c       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      @4000000052497be016a8c9f4       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      @4000000052497be016a8cddc       at java.lang.reflect.Method.invoke(Method.java:597)
      

      Cause

      The cause of this issue is that the Epic Status field is not configured correctly. Specifically, the field is expected to be configured with only one custom field context, which applies to issues in All Projects, with issue type Epic.

      If the field is configured with one context which selects specific projects and issue type Epic, the upgrade task will fail.

      Work around

      If the Epic Status field is in this configured state, it should not be "locked" (as it is a non-standard configuration). Therefore it should be possible to amend the configuration as follows:

      1. View all Custom Fields
      2. Find Epic Status and choose Configure
      3. Find the default custom field context (there should be only one) and Edit it
      4. At the bottom of the screen, under projects, choose Global Projects instead of selecting specific projects.
      5. Disable and re-enable the JIRA Agile plugin
      6. Re-indexing the instance

      The upgrade task should then succeed, and JIRA Agile functionality will be restored. This however may have the side effect of locking the Epic Status field from further updates. However, the initial configuration of the custom field context selecting specific projects is unsupported.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mtokar Michael Tokar
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: