Jira 10.1’s Support Exit
Jira Software 10.1 and Jira Service Management 10.1 reached the end of support on 9 October 2026, according to Atlassian’s policy. An installation may still be running, but that is not a reason to leave its next change without an owner.
A support deadline is not an outage
The policy provides two years of support after an initial feature or long-term support release, with no support after the relevant deadline. This is a Data Center version boundary, not a notice that Jira Cloud stopped operating. Atlassian recommends a current feature or long-term support release.
That distinction changes the question for a service owner. A successful login today shows that a particular interaction worked. It does not establish that the installed release is still supported, that the next maintenance window is booked or that a recovery plan has been tested. Treat those as separate checks rather than letting an apparently healthy service close the migration task.
Check both installations, not just the familiar one
Record the actual release of each product and who can approve its maintenance. Do not infer one installation’s status from another product’s inventory entry. The useful outcome is an explicit decision for each affected service: its destination, accountable owner, test window and recovery evidence.
Before selecting that destination, identify the apps, integrations and authentication arrangements on which the organisation depends. Agree which real workflows must remain usable and who will test them. Where a compatibility answer is missing, record the dependency and a date to resolve it; a guessed upgrade path is not a completed plan.
Close the change with evidence
A maintenance record should show the running release afterwards, the service owner’s acceptance and where the recovery evidence can be found. If the move cannot happen promptly, keep the exception visible with a responsible person and review date. These are BlackTree’s operational recommendations, not claims that a particular installation has been tested or compromised.
Updated on 15 October 2026 after the deadline passed. The original 6 October publication date and URL are unchanged.
