Upgrade/Downgrade Guide

Upgrade from Elements Connect 5 to Elements Connect 6

Firstly we recommend to do a backup of your Elements Connect 5 Configuration. To perform an Elements Connect backup please follow the backup and restore page.

To upgrade to V6:

You cannot upgrade directly from V5 to V6.11 and above, you need to add a step to an intermediary V6 version. Simply follow the same steps described bellow for the intermediary version - any version from V6.0.1 to V6.10.6 - and your final version.

Install the new version of Elements Connect with one of this 3 ways:
- by clicking on update button
- from an Elements Connect .obr file
- by searching the plugin from the Atlassian Marketplace.

After an install of the version 6 of Elements Connect the initial dependency check after the upgrade can fail. You can look at the "Dependency error" after upgrade to v6 page.

Downgrade from Elements Connect 6 to Elements Connect 5

Uninstall Elements Connect in Manage apps

Install manually the OBR of Elements Connect 5

Data loss

Field configuration

All changes made to the field configuration with Elements Connect 6 will be lost after the downgrade.

With Elements Connect v5, the field configurations are stored in the Plugin Settings, in v6 they are stored with Active Objects in Jira DB.

When v6 is installed, the field configuration is migrated to the new location, but the v5 configuration is preserved.
It means that when you downgrade to v5 from v6, you'll retrieve the configuration as it was before the upgrade.

Field values

All field values stored during Elements Connect 6 life cycle can't be read by Elements Connect 5.

With Elements Connect v6, values are stored in XML format, with v6 they are stored in JSON format.
Elements Connect v6 can read values stored with v5 but v5 can't read values stored with v6. See format storage page for more information.

Run this SQL query on Jira database to list all issues where a Connect field has been edited while the v6 version was installed:

SQL

select CONCAT(project.pkey, '-', issue.issuenum) as issuekey, cf.cfname, cfv.customfield as cfid
from customfieldvalue cfv, jiraissue issue, project, customfield cf
where cfv.customfield in 
  (select id
  from customfield
  where customfieldtypekey like 'com.valiantys.jira.plugins.SQLFeed%')
and cfv.textvalue like '{"keys"%'
and issue.id = cfv.issue
and project.id = issue.project
and cf.id = cfv.customfield

How to reactivate the UPM “Upload app” functionality

Since Jira versions 9.4.17, 9.12.4, 9.14.0 or higher, app installation through the Universal Plugin Manager (UPM) is disabled by default.

As a result, the “Upload app” button is no longer accessible and it’s no longer possible to downgrade apps.

Before:

After:

To reactivate this functionality, you need to set the upm.plugin.upload.enabled system property to true

Jira will need to be restarted to take this change into account.

Please see the following Atlassian documentation explaining how to proceed:

Multiple upgrade and downgrade

You have already upgraded and downgraded Elements Connect and you want to upgrade the product again to v6. Here are the specific steps to follow :

Go to your Jira database and delete the only entry in the table AO_*****_XML_MIGRATION_INFO (where ***** is a string variable according to your database).

SQL

DELETE FROM "AO_*****_XML_MIGRATION_INFO"

Install the new version of Elements Connect 6 with one of this 3 ways:
- by clicking on update button
- from an Elements Connect .obr file
- by searching the plugin from the Atlassian Marketplace.