You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have searched the forum for answers to this but not found anything concrete. Because we still have this page https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html which often gets asked about.
Atlassian supports feature versions for two years after the first major iteration of that version was released (for example, we support Jira Core 7.2.x for 2 years after Jira 7.2.0 was released).
For critical security bugs, please see our Security Bugfix Policy on which versions we will backport critical security fixes.
When a Critical security vulnerability is discovered by Atlassian or reported by a third party, Atlassian will do all of the following:
- Issue a new, fixed release for the current version of the affected product as soon as possible.
- Issue a new maintenance release for a previous version as follows:
Jira Software Server and Data Center
Jira Core Server and Data Center
Jira Service Management Server and Data Center (previously known as Jira Service Desk)
Confluence Server and Data Center
Bitbucket Server and Data Center
Bamboo Server and Data Center
BACK PORT POLICY
Issue new bug fix releases for:
- Any versions designated an 'Long Term Support release' that have not reached end of life.
- All feature versions released within 6 months of the date the fix is released.
The migration page and its FAQ contradicts what the end of life policy states.
After the end of support date, Atlassian and Marketplace Partners will no longer provide technical support for any issues, security updates, or bug fixes for critical vulnerabilities. Regular security updates help protect your business from threats and vulnerabilities, so we recommend moving to our Cloud or Data Center products before the end of support date.
Whenever this question get asked Atlassian employees answer that the end of life date applies only to Server products but Datacenter products will continue to be supported.
If that is the case why does every other policy and documentation still state that the server versions still receive bug fixes as long as the running version is supported as per the Atlassian Support End of Life Policy?
To add to this we have a new LTS release of Jira Datacenter, 9.12
And in the Atlassian End of Life Policy the latest version mentioned is 9.11
I understand if this can be confusing, but each link you cited is accurate.
Your ability to install updates in server and/or data center editions of our products is dependent upon the date your license expires.
In order for you to be able to install an updated version, your license has to have not expired on or before the date that exact version was released by Atlassian. We do create new version releases for up to 2 years for LTS (long term support) editions as you mentioned above. However, just because we release new versions, does not mean everyone is always entitled to them. As such, even if there is a critical security vulnerability found in a server product after the EOL of server products, Jira Admins won't be able to install that update with that expired license applied.
There is an important difference between server and data center in the terms of their licensing.
That said, we don't recommend running expired server versions, especially if exposed on the internet. Just because the terms of the license say you can keep using it after expiration, you won't have support for that product, and you can't upgrade it with that license applied. Should there be a critical security update for a server product found after the EOL date, you won't be able to install it while on the server license. This is why it's very important to either migrate to Cloud or upgrade to Data Center.
I hope this helps to clarify things.
So what does that mean for those instances running on lets say the latest LTS version of Confluence Server 8.5 with the EOL date 2025-08-22
So what happens after 2024-02-15?
They won't be able to install any update released after their license has expired. Ignore the EOL date of the product version. It's not directly correlated here since Atlassian is continuing to support Data Center editions of these products in those versions. The focus is on the license. All server licenses are expiring on 2024-02-15.
My interpretation of all this is that while new LTS Security Patches will be released, you will not be able to install them if your license has expired.
That is the case right now, if you let your maintenance expire in the past, you were still able to use the product, but you would be capped at the last version released before your maintenance expiry.
The End Of Server date simply means that no one will be able to have a maintenance license that goes beyond that date. Just now, we've renewed all of ours, but all of them expire on Feb 15 2024.
@Elvar Böðvarsson I can't reply on the other thread, but
DC and Server are the same product from a code perspective. It's all about the license. There are no separate releases for DC and for Server.
So what happens after 2024-02-15?
- Will Atlassian release security updates for Confluence Server 8.5 until the EOL date?
- Will those running Confluence Server 8.5 be able to install patches until the EOL date?
1) Yes, new security updates for Confluence 8.5 will be released until 2025-08-22
2) No, if you have a server license, you will not be able to install a Confluence version released after 2024-02-15