Jira Software · Lifecycle Status

Jira Software End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Jira Software versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Jira Software 10.0 reaches end of life on August 22, 2026. Plan your migration now — 13 days remaining.
Running an EOL version? Get matched with support options — free ↓
📅 Get reminded before Jira Software 10.0 reaches EOL on August 22, 2026 — alerts 90, 30 & 7 days out.
Google →
Latest Active
11.3.10
11.3 series
Next EOL
10.0
Aug 22, 2026
Active Versions
7
of 105 total
EOL Versions
93
no longer patched
35 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
25/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 200320042005200620072008200920102011201220132014201520162017201820192020202120222023202420252026202720281.01.11.21.31.42.12.22.32.42.52.63.03.13.23.33.43.53.63.73.83.93.103.113.123.134.04.14.24.34.45.05.15.26.06.16.26.36.47.07.17.27.37.47.57.67.77.87.97.107.117.127.138.08.18.28.38.48.58.68.78.88.98.108.118.128.138.148.158.168.178.188.198.208.218.229.09.19.29.39.49.59.69.79.89.99.109.119.129.139.149.159.169.1710.010.110.210.310.410.510.610.711.011.111.211.3TODAY
93 versions of Jira Software are past end of life — security patches have stopped. Get matched with support →
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1.0 1.0.0 Apr 10, 2002 Not published Past EOL EOL
1.1 1.1.0 Apr 30, 2002 Not published Past EOL EOL
1.2 1.2.0 May 21, 2002 Not published Past EOL EOL
1.3 1.3.3 Jul 4, 2002 Not published Past EOL EOL
1.4 1.4.1 Sep 10, 2002 Not published Past EOL EOL
2.1 2.1.0 Jun 3, 2003 Not published Past EOL EOL
2.2 2.2.1 Jun 20, 2003 Not published Past EOL EOL
2.3 2.3.0 Jul 3, 2003 Not published Past EOL EOL
2.4 2.4.0 Aug 20, 2003 Not published Past EOL EOL
2.5 2.5.3 Nov 12, 2003 Not published Past EOL EOL
2.6 2.6.1 Mar 3, 2004 Not published Past EOL EOL
3.0 3.0.3 Oct 12, 2004 Not published Past EOL EOL
3.1 3.1.1 Feb 14, 2005 Not published Past EOL EOL
3.2 3.2.3 May 27, 2005 Not published Past EOL EOL
3.3 3.3.3 Aug 5, 2005 Not published Past EOL EOL
3.4 3.4.3 Nov 15, 2005 Not published Past EOL EOL
3.5 3.5.3 Feb 1, 2006 Not published Past EOL EOL
3.6 3.6.5 Apr 18, 2006 Not published Past EOL EOL
3.7 3.7.4 Dec 18, 2006 Not published Past EOL EOL
3.8 3.8.1 Mar 13, 2007 Not published Past EOL EOL
3.9 3.9.3 May 8, 2007 Not published Past EOL EOL
3.10 3.10.2 Jul 9, 2007 Not published Past EOL EOL
3.11 3.11.0 Sep 25, 2007 Not published Past EOL EOL
3.12 3.12.3 Dec 7, 2007 Not published Past EOL EOL
3.13 3.13.5 Sep 9, 2008 Jul 21, 2011 5498 days past EOL EOL
4.0 4.0.2 Oct 6, 2009 Feb 26, 2012 5278 days past EOL EOL
4.1 4.1.2 Apr 7, 2010 Jun 18, 2012 5165 days past EOL EOL
4.2 4.2.4 Oct 19, 2010 Feb 8, 2013 4930 days past EOL EOL
4.3 4.3.4 Mar 16, 2011 May 27, 2013 4822 days past EOL EOL
4.4 4.4.5 Aug 2, 2011 Feb 22, 2014 4551 days past EOL EOL
5.0 5.0.7 Feb 22, 2012 Jul 1, 2012 5152 days past EOL EOL
5.1 5.1.8 Jul 9, 2012 Not published Past EOL EOL
5.2 5.2.11 Nov 11, 2012 Not published Past EOL EOL
6.0 6.0.8 May 21, 2013 Sep 3, 2015 3993 days past EOL EOL
6.1 6.1.9 Sep 23, 2013 May 22, 2016 3731 days past EOL EOL
6.2 6.2.7 Feb 24, 2014 Jun 11, 2016 3711 days past EOL EOL
6.3 6.3.15 Jul 8, 2014 Jul 8, 2016 3684 days past EOL EOL
6.4 6.4.14 Mar 16, 2015 Mar 17, 2017 3432 days past EOL EOL
7.0 7.0.11 Oct 1, 2015 Oct 6, 2017 3229 days past EOL EOL
7.1 7.1.10 Feb 10, 2016 Feb 10, 2018 3102 days past EOL EOL
7.2 7.2.15 Aug 23, 2016 Aug 23, 2018 2908 days past EOL EOL
7.3 7.3.9 Jan 2, 2017 Jan 3, 2019 2775 days past EOL EOL
7.4 7.4.6 Jun 28, 2017 Jun 29, 2019 2598 days past EOL EOL
7.5 7.5.4 Sep 5, 2017 Sep 6, 2019 2529 days past EOL EOL
7.6 LTS 7.6.17 Nov 15, 2017 Nov 14, 2019 2460 days past EOL EOL
7.7 7.7.4 Jan 10, 2018 Jan 11, 2020 2402 days past EOL EOL
7.8 7.8.4 Feb 19, 2018 Feb 20, 2020 2362 days past EOL EOL
7.9 7.9.2 Apr 8, 2018 Apr 9, 2020 2313 days past EOL EOL
7.10 7.10.2 May 28, 2018 May 29, 2020 2263 days past EOL EOL
7.11 7.11.2 Jul 10, 2018 Jul 11, 2020 2220 days past EOL EOL
7.12 7.12.3 Aug 26, 2018 Aug 27, 2020 2173 days past EOL EOL
7.13 LTS 7.13.18 Nov 27, 2018 Nov 28, 2020 2080 days past EOL EOL
8.0 8.0.3 Feb 8, 2019 Feb 11, 2021 2005 days past EOL EOL
8.1 8.1.3 Apr 3, 2019 Apr 4, 2021 1953 days past EOL EOL
8.2 8.2.6 May 20, 2019 May 21, 2021 1906 days past EOL EOL
8.3 8.3.5 Jul 21, 2019 Jul 22, 2021 1844 days past EOL EOL
8.4 8.4.3 Sep 8, 2019 Sep 9, 2021 1795 days past EOL EOL
8.5 LTS 8.5.19 Oct 21, 2019 Oct 21, 2021 1753 days past EOL EOL
8.6 8.6.1 Dec 16, 2019 Dec 17, 2021 1696 days past EOL EOL
8.7 8.7.1 Feb 2, 2020 Feb 3, 2022 1648 days past EOL EOL
8.8 8.8.1 Mar 18, 2020 Mar 19, 2022 1604 days past EOL EOL
8.9 8.9.1 May 18, 2020 May 20, 2022 1542 days past EOL EOL
8.10 8.10.1 Jun 22, 2020 Jun 23, 2022 1508 days past EOL EOL
8.11 8.11.1 Jul 14, 2020 Jul 15, 2022 1486 days past EOL EOL
8.12 8.12.3 Aug 25, 2020 Aug 26, 2022 1444 days past EOL EOL
8.13 LTS 8.13.27 Oct 6, 2020 Oct 8, 2022 1401 days past EOL EOL
8.14 8.14.1 Nov 22, 2020 Nov 23, 2022 1355 days past EOL EOL
8.15 8.15.1 Jan 21, 2021 Feb 2, 2023 1284 days past EOL EOL
8.16 8.16.2 Mar 22, 2021 Mar 23, 2023 1235 days past EOL EOL
8.17 8.17.1 May 17, 2021 May 18, 2023 1179 days past EOL EOL
8.18 8.18.2 Jul 21, 2021 Jul 1, 2023 1135 days past EOL EOL
8.19 8.19.1 Aug 25, 2021 Aug 26, 2023 1079 days past EOL EOL
8.20 LTS 8.20.30 Oct 19, 2021 Jan 31, 2024 921 days past EOL EOL
8.21 8.21.1 Dec 9, 2021 Dec 9, 2023 974 days past EOL EOL
8.22 8.22.6 Feb 16, 2022 Feb 16, 2024 905 days past EOL EOL
9.0 9.0.0 Jun 21, 2022 Jun 21, 2024 779 days past EOL EOL
9.1 9.1.1 Jul 21, 2022 Jul 21, 2024 749 days past EOL EOL
9.2 9.2.1 Aug 25, 2022 Aug 25, 2024 714 days past EOL EOL
9.3 9.3.3 Sep 28, 2022 Sep 29, 2024 679 days past EOL EOL
9.4 LTS 9.4.30 Nov 15, 2022 Jan 31, 2025 555 days past EOL EOL
9.5 9.5.1 Dec 6, 2022 Dec 6, 2024 611 days past EOL EOL
9.6 9.6.0 Jan 24, 2023 Jan 24, 2025 562 days past EOL EOL
9.7 9.7.2 Mar 20, 2023 Mar 20, 2025 507 days past EOL EOL
9.8 9.8.2 Apr 25, 2023 Apr 25, 2025 471 days past EOL EOL
9.9 9.9.2 Jun 2, 2023 Jun 2, 2025 433 days past EOL EOL
9.10 9.10.2 Jul 11, 2023 Jul 11, 2025 394 days past EOL EOL
9.11 9.11.3 Aug 30, 2023 Aug 30, 2025 344 days past EOL EOL
9.12 LTS 9.12.38 Nov 29, 2023 Nov 29, 2025 253 days past EOL EOL
9.13 9.13.1 Jan 22, 2024 Jan 22, 2026 199 days past EOL EOL
9.14 9.14.1 Feb 14, 2024 Feb 15, 2026 175 days past EOL EOL
9.15 9.15.2 Mar 27, 2024 Mar 27, 2026 135 days past EOL EOL
9.16 9.16.1 May 23, 2024 May 23, 2026 78 days past EOL EOL
9.17 9.17.5 Jun 26, 2024 Jun 26, 2026 44 days past EOL EOL
10.0 10.0.1 Aug 22, 2024 Aug 22, 2026 13 days remaining Warning
10.1 10.1.2 Oct 9, 2024 Oct 9, 2026 61 days remaining Warning
10.2 10.2.1 Nov 20, 2024 Nov 20, 2026 103 days remaining Warning
10.3 LTS 10.3.24 Dec 5, 2024 Dec 5, 2026 118 days remaining Warning
10.4 10.4.1 Jan 22, 2025 Jan 22, 2027 166 days remaining Warning
10.5 10.5.1 Mar 12, 2025 Mar 12, 2027 215 days remaining Active
10.6 10.6.1 Apr 23, 2025 Apr 23, 2027 257 days remaining Active
10.7 10.7.4 Jun 13, 2025 Jun 13, 2027 308 days remaining Active
11.0 11.0.1 Aug 13, 2025 Aug 13, 2027 369 days remaining Active
11.1 11.1.1 Sep 24, 2025 Sep 24, 2027 411 days remaining Active
11.2 11.2.1 Nov 6, 2025 Nov 6, 2027 454 days remaining Active
11.3 LTS 11.3.10 Dec 3, 2025 Dec 3, 2027 481 days remaining Active
Jira Software EOL status badge Live EOL badge for your README — updates automatically at every build. [![Jira Software EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Fjira-software.json)](https://endoflife.ai/jira-software)

What does Jira Software end of life mean for your organization?

When a version of Jira Software reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL Jira Software 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 Software 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.

OptionBest whenWatch 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.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Jira Software versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Get Jira Software Support Options

Jira Software has 93 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Jira Software exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.

Free · No obligation · Independent — we track the dates, vendors don't pay for placement · Dates verified against vendor sources
Frequently Asked Questions
What is the end-of-life date for Jira Software?
The next Jira Software version reaching EOL is 10.0 on August 22, 2026. See the full table above for all version EOL dates.
When is the Jira Software support end date?
The next Jira Software support end date is August 22, 2026, when version 10.0 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of Jira Software?
The latest active version of Jira Software is 11.3.10. Always verify against the table above as support windows can change.
What happens when Jira Software reaches end of life?
When Jira Software reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Jira Software?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Jira Software versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →
Jira Software end-of-life status badge