I received a notice of some high priority issues in Jiea 9.12 that resulted in the creation of 9.12.28 for Jira Server. I applied this update to my test layer and was informed, upon starting Jira Server, that it cannot be started because it was created after my license has lapsed. However, to my knowledge, Atlassian stopped providing licenses for Jira Server a couple years ago. As such, wouldn't that make every Jira Server instance unable to perform the upgrade?
Can Jira Server 9.12.28 be made generally available?
Hi @Michael Roalkvam
Welcome to the Atlassian community!
- Jira Server 9.12.28 cannot be applied if your Server license has expired.
Atlassian policy: You can keep using Jira after license expiry, but you cannot upgrade to any version released after your maintenance end date.
https://support.atlassian.com/jira/kb/what-happens-when-your-jira-server-or-data-center-license-expires/
-Jira Server support ended on Feb 15, 2024, so no new Server licenses or renewals are available.
- 9.12.x is the final LTS line for Server, but each build (like 9.12.28) still checks license validity by release date.
https://confluence.atlassian.com/jirasoftware/jira-software-9-12-x-release-notes-1319575972.html?
- If your license expired before the 9.12.28 release, Jira will show the “created after license lapsed” message and refuse to start.
- To resolve: stay on the latest eligible 9.12.x build (before your maintenance end date) or migrate to Jira Data Center / Cloud.
Hello @Gor Greyan
Thank you for providing a long and detailed re-explanation of the answer I provided... that the OP can't do that upgrade.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Andrew Edwards
Just expanding on your answer with supporting references, so future readers have the full context.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OK, thanks @Gor Greyan
I just chose to provide a more direct and succinct answer to the OP's question, rather than cut-n-paste the same old common knowledge response that any public LLM type AI will happily regurgitate.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Andrew Edwards
Thanks for providing that direct answer.
What did you find wrong or old in my answer, for continuing this topic?
It wasn’t a copy-paste — it was written from official Atlassian sources to support and expand on your point.
Have a good weekend, brother :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There was nothing wrong with the answer, it was absolutely correct.
I just feel that the same questions about Jira Server have been asked so many times on this and other forums, and the same answer has been provided so many times, and Atlassian have provided so much supporting documentation already, that the whole topic can now be considered to be common knowledge that is readily available and instantly findable by anyone using any well-known public search or AI tool.
From my point of view, it really doesn't need to be 're-explained' again.
Let's consider this discussion closed, OK, as we're now just debating a difference of opinion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Michael Roalkvam
Can Jira Server 9.12.28 be made generally available?
You've sort of answered your own question...
However, to my knowledge, Atlassian stopped providing licenses [and support] for Jira Server a couple years ago.
That's correct
As such, wouldn't that make every Jira Server instance unable to perform the upgrade?
That's correct.
End of support means just that :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.