Upgrading to JIRA Agile 6.3.2 breaks JIRA Agile

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

After upgrading JIRA Agile to version 6.3.2, JIRA Agile stops working, and the following error is present in the UI :

 

JIRA Agile is currently unavailable. This might be because an upgrade task has failed to run or has not not yet completed.

 

The following appears in the atlassian-jira.log:

2013-09-26 20:00:17,911 pool-103-thread-1 ERROR admin 1198x2390x3 et6e7x 10.60.2.87 /rest/plugins/1.0/ [sal.core.upgrade.PluginUpgrader] Upgrade failed: com.pyxis.greenhopper.jira.fields.NotSupported cannot be cast to com.pyxis.greenhopper.jira.fields.CustomIssueField
java.lang.ClassCastException: com.pyxis.greenhopper.jira.fields.NotSupported cannot be cast to com.pyxis.greenhopper.jira.fields.CustomIssueField
	at com.atlassian.greenhopper.service.issue.DefaultFieldsServiceImpl.getBusinessValueCustomField(DefaultFieldsServiceImpl.java:62)
	at com.atlassian.greenhopper.upgrade.GhUpgradeTask040.updateBusinessValueField(GhUpgradeTask040.java:317)
	at com.atlassian.greenhopper.upgrade.GhUpgradeTask040.performUpgrade(GhUpgradeTask040.java:105)
	at com.atlassian.greenhopper.upgrade.AbstractGhUpgradeTask.doUpgrade(AbstractGhUpgradeTask.java:62)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  <+2> (NativeMethodAccessorImpl.java:39) (DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)

Diagnosis

One of the fields required for the upgrade task is missing, hence causing the stack trace.

Cause

The 'Business Value' custom field is missing, but is required in the upgrade task. Hence, the upgrade task fails, and causes JIRA Agile to be unusable.

Workaround

  1. Navigate to the 'Custom Fields' section of your JIRA Administration, and re-create a 'Business Value' custom field (ensure that it is a Number Field)
  2. Shut down your JIRA
  3. Access your database, and run the following query :

    select id from customfield where cfname = 'Business Value';

    Take note of the ID of the customfield

  4. Next, run the following query :

    select 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.

     

  5. Modify the XML output from the previous step (using the text editor) to so that the entry for Business Value points to the right custom field id which we identified in step 3. An example of an entry is as follows :

      <entry>
        <string>gh.issue.businessvalues</string>
        <string>customfield_10100</string>
      </entry>
  6. Once the XML is prepared, update back the database with the below SQL command: 

    update 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');
  7. Once everything is done, restart your JIRA instance, and your JIRA Agile should work now

Resolution

It is currently being tracked as a bug here :  GHS-9869 - Getting issue details... STATUS

Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.