Security updates after expired licence (within same minor version) allowed?

[Matthias Kannenberg]

One of my clients has an older Jira installation for a project and since the project is in a ramp-down/maintenance state is not interested in renewing their license which expired some time ago (around version 8.1.1).

Would it be possible to upgrade their Jira to 8.1.3 (the security fix for the latest Jira security advisory) even if this came out after the license expired (but stays within the same minor version) or is there no way to have a secure installation when the license expired?

All documentation only mentions the expiry date as the cut-off date for what versions are allowed but under that model why publish versions like 8.1.3 in the first place if you can upgrade to newer major/minor versions anyway.

[Daniel Eads]

Hey @Matthias Kannenberg ,

I think you may have gotten your answer from Deniz already but just wanted to post clearly for potential newcomers on the question. You can download any version that was released while your maintenance period is still valid. As an example, say your maintenance period expires May 1. Here are some hypothetical releases:

• 6.7.3, released on April 17. Eligible
• 6.7.5, released June 19. Not eligible

So for the latest advisories in particular, your client's maintenance needs to have been valid through September 17, 2019 in order to download the versions that fix the issue. If the maintenance period ended before that date, they will need to renew their support maintenance in order to upgrade to the fixed versions.

Cheers,
Daniel

[Deniz Oğuz - The Starware]

All 8.1.x releases are compatible with each other. Even if marketplace marks 3rd party add-ons as compatible with newer bug fix version automatically.  But it is not the case with minor version upgrades, you are required to check release notes and try to understand what is changed between two different minor version upgrades. This is called semantic versioning. So I think they are releasing this security release for their customers who don't want to upgrade to newer minor version due to possible compatibility issues etc.

[Matthias Kannenberg]

Okay, just to be sure that I'm not misunderstanding your answer: While you tried to explain why Atlassian does security releases for older version you did not cover my actual question (If I can use a security update with en expired license if I'm eligible for this minor version) in any way, right?

[Deniz Oğuz - The Starware]

Unfortunately security releases are no different than normal releases in terms of licensing.