JIRA Agile fails to be enabled during restart

Summary

In Jira Software, Jira Agile app fails to be enabled. The following appears in theatlassian-jira.log:

Diagnosis

• Run the following SQL statement. propertyvalue column should return an XML entry.

  1 2 3 select * from propertyentry pe inner join propertytext pt on pe.id = pt.id where (pe.entity_name like 'GreenHopper.Run.History' or pe.entity_name like 'GreenHopper.UpgradeHistory');

• Any other entry that does not return an XML can be considered as problematic

  Expected entry

  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 <map> <entry> <string>pluginVersion</string> <string>8.20.10</string> </entry> <entry> <string>ranOn</string> <string>2022-09-01T10:49:14.398+02:00</string> </entry> <entry> <string>buildDate</string> <string>2022-06-22T16:16:50.081+02:00</string> </entry> <entry> <string>latestUpgradeTaskRun</string> <string>0</string> </entry> <entry> <string>changeSet</string> <string>b92c120b3532fd60</string> </entry> </map>

• The following result is just an example of an problematic entry

  Problematic entry

  1 <style> h1{backgroundcolor:red}</style> <h1> New version will be released on 1.9. migrated to the cloud from 3:00 p.m </h1>

Cause

Jira Software's configurations are stored as XML within the database. With that, if the XML is invalid for any reason (eg. manually modified, corrupted, etc), it can result in the above error.

Solution

1. Restore Jira database to a pre-corruption state

2. If restoring a previous Jira backup is not possible, you could attempt to delete these entries in both propertyentry and propertytext tables but if other records are still corrupted, you would face other unknown issues

   Atlassian Support cannot guarantee to provide any support for the steps described on this page as direct data manipulation is not covered under Atlassian Support Offerings. Please be aware that this material is provided for your information only and that you use it at your own risk.

   Always back up your data before performing any modifications to the database. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.

   1. Stop JIRA

   2. Backup Jira database

   3. Run the following SQL to remove the content. You need to replace pt1.propertyvalue value for the one identified using the Diagnosis query.

      These queries were written for Postgres and may have to be updated to work on another database:

      1. Query #1 - Get propertyentry Ids to be deleted. Copy those Ids. Those Ids will be needed for Query#3

         1 2 3 4 select pe.id from propertyentry pe inner join propertytext_1 pt1 on pe.id = pt1.id where (pe.entity_name like 'GreenHopper.Run.History' or pe.entity_name like 'GreenHopper.UpgradeHistory') and pt1.propertyvalue ='<style> h1{backgroundcolor:red}</style> <h1> New version will be released on 1.9. migrated to the cloud from 3:00 p.m </h1>';

      2. Query #2 - Delete propertytext table entries

         1 2 3 4 5 delete from propertytext pt where id in ( select pe.id from propertyentry pe inner join propertytext pt1 on pe.id = pt1.id where (pe.entity_name like 'GreenHopper.Run.History' or pe.entity_name like 'GreenHopper.UpgradeHistory') and pt1.propertyvalue ='<style> h1{backgroundcolor:red}</style> <h1> New version will be released on 1.9. migrated to the cloud from 3:00 p.m </h1>';

      3. Query #3 - Delete propertyentry table entries

         1 delete from propertyentry where id in (paste here all Ids from Query#1);

   4. Start Jira