Jira Service Management End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Jira Service Management versions. Data from endoflife.date, checked against the vendor's own lifecycle pages where we have read them (share on /accuracy). Updated at every deploy.
Jira Service Management 11.3 is supported until December 3, 2027, its end-of-support date. The next Jira Service Management version to reach end of life is 10.2, on November 20, 2026. 60 of 70 tracked Jira Service Management versions are past end of life; the most recent to reach it, 10.1, did so on October 9, 2026. The full Jira Service Management lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓GET https://api.endoflife.ai/v1/score/jira-service-management/10.2 returns this version's end-of-life date, its source and the EOL Risk Score as JSON. Get a free API key (150 requests a day, no expiry).| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.0 | 3.0.11 | Oct 1, 2015 | Oct 6, 2017 | 3331 days past EOL | EOL |
| 3.1 | 3.1.10 | Feb 10, 2016 | Feb 11, 2018 | 3203 days past EOL | EOL |
| 3.2 | 3.2.15 | Aug 23, 2016 | Aug 23, 2018 | 3010 days past EOL | EOL |
| 3.3 | 3.3.1 | Jan 3, 2017 | Jan 3, 2019 | 2877 days past EOL | EOL |
| 3.4 | 3.4.2 | Mar 13, 2017 | Mar 14, 2019 | 2807 days past EOL | EOL |
| 3.5 | 3.5.3 | Apr 26, 2017 | Apr 27, 2019 | 2763 days past EOL | EOL |
| 3.6 | 3.6.4 | Jun 29, 2017 | Jun 29, 2019 | 2700 days past EOL | EOL |
| 3.7 | 3.7.2 | Sep 4, 2017 | Sep 4, 2019 | 2633 days past EOL | EOL |
| 3.8 | 3.8.5 | Sep 5, 2017 | Sep 6, 2019 | 2631 days past EOL | EOL |
| 3.9 LTS | 3.9.17 | Nov 16, 2017 | Nov 16, 2019 | 2560 days past EOL | EOL |
| 3.10 | 3.10.4 | Jan 11, 2018 | Jan 11, 2020 | 2504 days past EOL | EOL |
| 3.11 | 3.11.4 | Feb 20, 2018 | Feb 20, 2020 | 2464 days past EOL | EOL |
| 3.12 | 3.12.2 | Apr 9, 2018 | Apr 9, 2020 | 2415 days past EOL | EOL |
| 3.13 | 3.13.2 | May 29, 2018 | May 29, 2020 | 2365 days past EOL | EOL |
| 3.14 | 3.14.2 | Jul 11, 2018 | Jul 11, 2020 | 2322 days past EOL | EOL |
| 3.15 | 3.15.3 | Aug 27, 2018 | Aug 27, 2020 | 2275 days past EOL | EOL |
| 3.16 LTS | 3.16.18 | Nov 28, 2018 | Nov 28, 2020 | 2182 days past EOL | EOL |
| 4.0 LTS | 4.0.3 | Feb 11, 2019 | Feb 11, 2021 | 2107 days past EOL | EOL |
| 4.1 | 4.1.3 | Apr 4, 2019 | Apr 4, 2021 | 2055 days past EOL | EOL |
| 4.2 | 4.2.6 | May 21, 2019 | May 21, 2021 | 2008 days past EOL | EOL |
| 4.3 | 4.3.5 | Jul 22, 2019 | Jul 22, 2021 | 1946 days past EOL | EOL |
| 4.4 | 4.4.3 | Sep 9, 2019 | Sep 9, 2021 | 1897 days past EOL | EOL |
| 4.5 LTS | 4.5.19 | Oct 21, 2019 | Oct 21, 2021 | 1855 days past EOL | EOL |
| 4.6 | 4.6.1 | Dec 17, 2019 | Dec 17, 2021 | 1798 days past EOL | EOL |
| 4.7 | 4.7.1 | Feb 3, 2020 | Feb 3, 2022 | 1750 days past EOL | EOL |
| 4.8 | 4.8.1 | Mar 19, 2020 | Mar 19, 2022 | 1706 days past EOL | EOL |
| 4.9 | 4.9.1 | May 20, 2020 | May 20, 2022 | 1644 days past EOL | EOL |
| 4.10 | 4.10.1 | Jun 23, 2020 | Jun 23, 2022 | 1610 days past EOL | EOL |
| 4.11 | 4.11.1 | Jul 15, 2020 | Jul 15, 2022 | 1588 days past EOL | EOL |
| 4.12 | 4.12.3 | Aug 26, 2020 | Aug 26, 2022 | 1546 days past EOL | EOL |
| 4.13 LTS | 4.13.27 | Oct 8, 2020 | Nov 8, 2022 | 1472 days past EOL | EOL |
| 4.14 | 4.14.1 | Nov 23, 2020 | Nov 23, 2022 | 1457 days past EOL | EOL |
| 4.15 | 4.15.1 | Jan 21, 2021 | Feb 2, 2023 | 1386 days past EOL | EOL |
| 4.16 | 4.16.2 | Mar 23, 2021 | Mar 23, 2023 | 1337 days past EOL | EOL |
| 4.17 | 4.17.1 | May 18, 2021 | May 18, 2023 | 1281 days past EOL | EOL |
| 4.18 | 4.18.2 | Jul 1, 2021 | Jul 1, 2023 | 1237 days past EOL | EOL |
| 4.19 | 4.19.1 | Aug 26, 2021 | Aug 26, 2023 | 1181 days past EOL | EOL |
| 4.20 LTS | 4.20.30 | Oct 19, 2021 | Jan 31, 2024 | 1023 days past EOL | EOL |
| 4.21 | 4.21.1 | Dec 9, 2021 | Dec 9, 2023 | 1076 days past EOL | EOL |
| 4.22 | 4.22.6 | Feb 16, 2022 | Feb 16, 2024 | 1007 days past EOL | EOL |
| 5.0 | 5.0.0 | Jun 21, 2022 | Jun 21, 2024 | 881 days past EOL | EOL |
| 5.1 | 5.1.1 | Jul 21, 2022 | Jul 21, 2024 | 851 days past EOL | EOL |
| 5.2 | 5.2.1 | Aug 25, 2022 | Aug 25, 2024 | 816 days past EOL | EOL |
| 5.3 | 5.3.3 | Sep 29, 2022 | Sep 29, 2024 | 781 days past EOL | EOL |
| 5.4 LTS | 5.4.30 | Nov 15, 2022 | Jan 31, 2025 | 657 days past EOL | EOL |
| 5.5 | 5.5.1 | Dec 6, 2022 | Dec 6, 2024 | 713 days past EOL | EOL |
| 5.6 | 5.6.0 | Jan 24, 2023 | Jan 24, 2025 | 664 days past EOL | EOL |
| 5.7 | 5.7.2 | Mar 20, 2023 | Mar 20, 2025 | 609 days past EOL | EOL |
| 5.8 | 5.8.2 | Apr 25, 2023 | Apr 25, 2025 | 573 days past EOL | EOL |
| 5.9 | 5.9.2 | Jun 2, 2023 | Jun 2, 2025 | 535 days past EOL | EOL |
| 5.10 | 5.10.2 | Jul 11, 2023 | Jul 11, 2025 | 496 days past EOL | EOL |
| 5.11 | 5.11.3 | Aug 30, 2023 | Aug 30, 2025 | 446 days past EOL | EOL |
| 5.12 LTS | 5.12.40 | Nov 29, 2023 | Nov 29, 2025 | 355 days past EOL | EOL |
| 5.13 | 5.13.1 | Jan 22, 2024 | Jan 22, 2026 | 301 days past EOL | EOL |
| 5.14 | 5.14.1 | Feb 13, 2024 | Feb 15, 2026 | 277 days past EOL | EOL |
| 5.15 | 5.15.2 | Mar 27, 2024 | Mar 27, 2026 | 237 days past EOL | EOL |
| 5.16 | 5.16.1 | May 23, 2024 | May 23, 2026 | 180 days past EOL | EOL |
| 5.17 | 5.17.5 | Jun 26, 2024 | Jun 26, 2026 | 146 days past EOL | EOL |
| 10.0 | 10.0.1 | Aug 22, 2024 | Aug 22, 2026 | 89 days past EOL | EOL |
| 10.1 | 10.1.2 | Oct 9, 2024 | Oct 9, 2026 | 41 days past EOL | EOL |
| 10.2 | 10.2.1 | Nov 20, 2024 | Nov 20, 2026 | 1 day remaining | Warning |
| 10.3 LTS | 10.3.26 | Dec 5, 2024 | Dec 5, 2026 | 16 days remaining | Warning |
| 10.4 | 10.4.1 | Jan 22, 2025 | Jan 22, 2027 | 64 days remaining | Warning |
| 10.5 | 10.5.1 | Mar 12, 2025 | Mar 12, 2027 | 113 days remaining | Warning |
| 10.6 | 10.6.1 | Apr 23, 2025 | Apr 23, 2027 | 155 days remaining | Warning |
| 10.7 | 10.7.4 | Jun 17, 2025 | Jun 13, 2027 | 206 days remaining | Active |
| 11.0 | 11.0.1 | Aug 13, 2025 | Aug 13, 2027 | 267 days remaining | Active |
| 11.1 | 11.1.1 | Sep 24, 2025 | Sep 24, 2027 | 309 days remaining | Active |
| 11.2 | 11.2.1 | Nov 6, 2025 | Nov 6, 2027 | 352 days remaining | Active |
| 11.3 LTS | 11.3.12 | Dec 3, 2025 | Dec 3, 2027 | 379 days remaining | Active |
[](https://endoflife.ai/jira-service-management)
Jira Service Management release and support pattern
Across the 70 release lines with a published release date, Jira Service Management has shipped a new line roughly every 2 months (median interval). A line typically stays supported for about 2 years from its release to its end-of-life date. 10 of the 70 tracked lines are designated long-term support, which is where the longer windows sit.
Of the 70 release lines tracked, 60 are past end of life and 10 are still within support. The newest line, 11.3, was released December 3, 2025. The next scheduled end of life is 10.2 on November 20, 2026 — 1 day from this build. The longest-supported line currently published is 11.3, to December 3, 2027.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Jira Service Management security intelligence
CISA KEV history: Jira Service Management is named in CISA's Known Exploited Vulnerabilities catalog 1 time, most recently on 2026-10-15. Derived from CISA's live catalog at every build.
What does Jira Service Management end of life mean for your organization?
When a version of Jira Service Management reaches end of life, the vendor's standard security patches for that version stop. Vulnerabilities found after that date are still published on the National Vulnerability Database, exploit code often becomes public, and systems on that version stay exposed until they are upgraded or covered by extended support.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but the vendor's policy provides no patch for the ended version. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Jira Service Management should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Jira Service Management reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your Jira Service Management version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
Jira Service Management has 60 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Jira Service Management is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."