Upgrade Jira 8.2.4 "Jira Core must be updated to be compatible with this version of Jira Software"

[Deleted user]

Hi,

after upgrading Jira Software 8.2.2 to 8.2.4 using the Linux installer the following error appears at "Administration > Applications > Versions & Licenses":

"Jira Core must be updated to be compatible with this version of Jira Software."

The error appears although both Jira Software and Jira Core are version 8.2.4 as you can see in the screenshot.

I also tried manually upgrading Jira Core by using the Jira Core installer atlassian-jira-core-8.2.4-x64.bin but the error still shows up.

[Thomas Deiler · Accepted solution]

See also

Error message when updating license key in an updated version of Jira

and

Update from Jira 8.2.3 to 8.2.4, need to update Core?

[Thomas Deiler]

Dear all,

please refer to JRASERVER-69641 the issue seems to be fixed. They modified the marketplace. If it is still not working, please comment this issue, for those with a starter license.

So long

Thomas

[Deleted user]

Hi Thomas,

thank you for the additional info. I can confirm that the issue is resolved.

Best regards

fro

[Mirek]

Please take a look on this ticket: https://jira.atlassian.com/browse/JRASERVER-63794

[Deleted user]

Hello Mirek,

that doesn't help in this case. In JRASERVER-63794 the versions of Jira Software and Jira Core are different (e. g. 7.2.3 and 7.2.0).

In my case Jira Software and Jira Core are exactly the same (8.2.4).

Best regards

fro

[Mirek]

It is related to "JIRA 7.2 onwards" so it might also affect the latest releases. Anyway someone might not update the ticket. What is important is the resolution or workaround which in this case is saying something about your version (8.2.4) ..

There should be no impact in functionality, if you previously had this configuration and are just seeing this message.

Alternatively, upgrade you version of JIRA Software or JIRA Service desk using the installer. See Upgrading JIRA Applications for full details.

This was also affecting 8.2.4 on 7/18/2019 but has been fixed through a Marketplace update.