In order to import a project from a different instance, we upgraded JIRA from version 7.6 to 7.12.3. But after the upgrade I got the following error: " * The backup project 'BSS OCB' requires custom field named 'Epic Colour' with full key 'com.pyxis.greenhopper.jira:gh-epic-color'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'. * The backup project 'BSS OCB' requires custom field named 'Epic Link' with full key 'com.pyxis.greenhopper.jira:gh-epic-link'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'. * The backup project 'BSS OCB' requires custom field named 'Epic Name' with full key 'com.pyxis.greenhopper.jira:gh-epic-label'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'. * The backup project 'BSS OCB' requires custom field named 'Epic Status' with full key 'com.pyxis.greenhopper.jira:gh-epic-status'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'. * The backup project 'BSS OCB' requires custom field named 'Rank (Obsolete)' with full key 'com.pyxis.greenhopper.jira:gh-global-rank'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'. * The backup project 'BSS OCB' requires custom field named 'Rank' with full key 'com.pyxis.greenhopper.jira:gh-lexo-rank'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'. * The backup project 'BSS OCB' requires custom field named 'Release Version History' with full key 'com.pyxis.greenhopper.jira:greenhopper-releasedmultiversionhistory'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'. * The backup project 'BSS OCB' requires custom field named 'Sprint' with full key 'com.pyxis.greenhopper.jira:gh-sprint'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'. How can i solve this plugin compatibility error ? Thanks

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Project Import plugins compatibility problem after jira upgrade

Ziad Bakhiet

In order to import a project from a different instance, we upgraded JIRA from version 7.6 to 7.12.3. But after the upgrade I got the following error:

The backup project 'BSS OCB' requires custom field named 'Epic Colour' with full key 'com.pyxis.greenhopper.jira:gh-epic-color'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'.
The backup project 'BSS OCB' requires custom field named 'Epic Link' with full key 'com.pyxis.greenhopper.jira:gh-epic-link'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'.
The backup project 'BSS OCB' requires custom field named 'Epic Name' with full key 'com.pyxis.greenhopper.jira:gh-epic-label'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'.
The backup project 'BSS OCB' requires custom field named 'Epic Status' with full key 'com.pyxis.greenhopper.jira:gh-epic-status'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'.
The backup project 'BSS OCB' requires custom field named 'Rank (Obsolete)' with full key 'com.pyxis.greenhopper.jira:gh-global-rank'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'.
The backup project 'BSS OCB' requires custom field named 'Rank' with full key 'com.pyxis.greenhopper.jira:gh-lexo-rank'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'.
The backup project 'BSS OCB' requires custom field named 'Release Version History' with full key 'com.pyxis.greenhopper.jira:greenhopper-releasedmultiversionhistory'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'.
The backup project 'BSS OCB' requires custom field named 'Sprint' with full key 'com.pyxis.greenhopper.jira:gh-sprint'. In the current instance of Jira the plugin is at version '7.6.0-DAILY20171103151351', but in the backup it is at version '7.12.0-DAILY20180906101548'.

How can i solve this plugin compatibility error ?

Thanks

Accepted answers

Andy Heinzer

Hi Ziad,

I understand that you have recently upgraded your Jira from a 7.6 to a 7.12 version, in order to import a project from a separate 7.12 backup file.

However the error messages you see here would tend to indicate that your upgrade has not been completed yet, at least not for Jira Software. It's possible that perhaps you have updated Jira Core to this 7.12 version, but Jira Software will operate like a plugin, and in turn when you upgrade Jira Core first, you then have to update Jira Software to allow it to update your data.

On your destination Jira site, try going to the Gear Icon -> Applications -> Versions and Licenses. I'd be interested to see what version of Jira Software is reported here and if there are any error messages on this page. If my suspicious is correct, and Jira Core has already been upgraded, then you can just update Jira Software directly on this page without having to restart Jira.

If this doesn't help, then I'd be interested to see if you can restart Jira and then if we could see what a startup looks like in your $JIRAHOME/log/atlassian-jira.log This file can tell us more about the specific versions of plugins that are being loaded by Jira at startup time. If the 7.12.x Jira Software plugin is not loading for some reason, it too could explain this error, and the logs should give us some clues as to how we can address this problem.