Jira 10.3 End of Life: December 5, 2026 (Jira Software and JSM)
Jira Software Data Center 10.3 reaches end of life on December 5, 2026. Jira Service Management Data Center 10.3 reaches end of life on December 5, 2026, the same day. Atlassian's End of Support Policy lists 10.3 with that end of support (EOS) date for each product, and labels both lines Long Term Support. Atlassian's term on that page is end of support. Its Jira Software 10.3 release notes call the same day the end of life (EOL) date. The policy says: "Atlassian does not provide support for releases that have reached their end of support (EoS) date."
Key Dates at a Glance
- Jira Software 10.3 (LTS): end of life 2026-12-05
- Jira Service Management 10.3 (LTS): end of life 2026-12-05
- Jira Software 10.3: released 2024-12-05
- Jira Software 10.4: end of life 2027-01-22
- Jira Software 10.5: end of life 2027-03-12
- Jira Software 10.6: end of life 2027-04-23
- Jira Software 10.7: end of life 2027-06-13
- Jira Software 11.3 (LTS): end of life 2027-12-03
- Jira Service Management 11.3 (LTS): end of life 2027-12-03
- Atlassian Data Center (Jira Software, Jira Service Management): end of life 2029-03-28
- CVE-2026-21589: added to CISA KEV 2026-10-15
Jira 10.x and 11.x end-of-life dates, both products
Each date is the end of support (EOS) date in Atlassian's End of Support Policy. The same dates are served on our Jira Software and Jira Service Management pages. The label column is Atlassian's own: it prints LONG TERM SUPPORT next to two lines and nothing next to the others.
| Line | Atlassian's label | Jira Software Data Center | Jira Service Management Data Center |
|---|---|---|---|
| 11.3 | Long Term Support | December 3, 2027 | December 3, 2027 |
| 11.2 | No label | November 6, 2027 | November 6, 2027 |
| 11.1 | No label | September 24, 2027 | September 24, 2027 |
| 11.0 | No label | August 13, 2027 | August 13, 2027 |
| 10.7 | No label | June 13, 2027 | June 13, 2027 |
| 10.6 | No label | April 23, 2027 | April 23, 2027 |
| 10.5 | No label | March 12, 2027 | March 12, 2027 |
| 10.4 | No label | January 22, 2027 | January 22, 2027 |
| 10.3 | Long Term Support | December 5, 2026 | December 5, 2026 |
| 10.2 | No label | November 20, 2026 | November 20, 2026 |
| 10.1 | No label | October 9, 2026 | October 9, 2026 |
| 10.0 | No label | August 22, 2026 | August 22, 2026 |
Lines 10.0, 10.1 and 10.2 passed their dates before this guide was published. 10.3 is next. The line links go to our Jira Software version pages. The Jira Service Management version pages are linked from the Jira Service Management lifecycle page.
What Atlassian's policy says ends that day
Atlassian's End of Support Policy has one rule for these releases: "Atlassian supports releases for two years after the initial feature or Long-Term Support (LTS) release." Both sets of 10.3 release notes print the day 10.3.0 was released: December 5, 2024 for Jira Software and December 5, 2024 for Jira Service Management. Two years on is the end-of-life date.
- Support. The policy says: "Atlassian does not provide support for releases that have reached their end of support (EoS) date." The Jira Software 10.3 release notes say the same in other words: "Once a version reaches its end of life (EOL), we'll no longer provide support for it."
- Bug-fix releases. The Jira Service Management 10.3 release notes say what the Long Term Support label means for 10.3: "we'll provide bug-fix releases until 10.3 reaches end of life, to address critical security, stability, data integrity, and performance issues." Atlassian's Long Term Support releases page makes the same commitment for every such release: "Make bug fix releases available for the designated version until it reaches end-of-life."
- Critical security fixes. Atlassian's Security Bug Fix Policy says that for a critical vulnerability in Jira Software or Jira Service Management it issues new bug fix releases for two groups. The first is versions designated a Long Term Support release "that have not reached end of life". The second is "All feature versions released within 6 months of the date the fix is released." The policy's own example names Jira Software 10.3.x "because 10.3.0 is the previous Long Term Support release". After its end-of-life date 10.3 is in neither group.
What the policy does not say. The End of Support Policy is about support. It does not say that a 10.3 installation stops running on that day. It also does not rule out a later build. Atlassian's advisory for CVE-2026-21589, published on October 5, 2026, names a fixed build on the Jira Software 9.12 line, and the Jira Software release notes give the 9.12 end-of-life date as November 29, 2025. Nothing in the policy commits Atlassian to do the same for 10.3.
Is Jira 10.3 a Long Term Support release?
Yes, for both products. Atlassian's End of Support Policy prints its LONG TERM SUPPORT label next to 10.3 in the Jira Software list and in the Jira Service Management list. The release notes say "Jira Software 10.3 is a Long Term Support release" and "Jira Service Management 10.3 is a Long Term Support release". Our data marks 10.3 as LTS for both products as well.
The label does not buy more time. Atlassian's Long Term Support releases page says: "The Long Term Support release will be supported for the same period of time as outlined in the Atlassian Support End of Life Policy, which is 2 years." What the label buys is the bug-fix commitment described above. The same page says Atlassian will designate a feature release as a Long Term Support release at least once every 12 months.
Which release to move to
Jira 11.3, for both products. On the day this guide was published, 11.3 was the newest line in Atlassian's End of Support Policy for Jira Software and for Jira Service Management, and both carry the LONG TERM SUPPORT label. Jira Software 11.3 ends on December 3, 2027 and Jira Service Management 11.3 on December 3, 2027. The policy's own advice is: "Atlassian recommends upgrading to the latest feature or LTS release." Atlassian's Security Bug Fix Policy describes 11.3.0 as "both the latest feature and Long Term Support release", so for Jira that advice points at one line.
The lines in between are weaker choices, for two reasons.
- They end sooner. For Jira Software, 10.4 ends on January 22, 2027, 10.5 on March 12, 2027, 10.6 on April 23, 2027, 10.7 on June 13, 2027, 11.0 on August 13, 2027, 11.1 on September 24, 2027 and 11.2 on November 6, 2027. The Jira Service Management dates are in the table above.
- They fall out of the critical security fix groups. Under the Security Bug Fix Policy quoted above, a feature version is covered when it was released within 6 months of the fix. Atlassian's advisory for CVE-2026-21589 shows the effect. For Jira Software it names fixed builds on the 9.12, 10.3 and 11.3 lines only. For Jira Service Management it names fixed builds on the 5.12, 10.3 and 11.3 lines only. Our CVE-2026-21589 guide lists the lines that have none.
Read the 11.3 release notes before you schedule the upgrade. The Jira Software 11.3 release notes say: "This version of Jira runs only on Java 21." They carry a section on supported platforms changes, and they say 11.3 contains all features introduced since the last LTS version, Jira 10.3. Atlassian's Long Term Support releases page links the release notes and a change log for Jira Service Management 11.3.
How the Data Center end of life bears on the choice
The version dates are one clock. Atlassian has set a second one for the product itself. Its Data Center end of life page sets end of life for the impacted Data Center products on March 28, 2029, and lists Jira Software Data Center and Jira Service Management Data Center among them. The page says Data Center subscriptions expire on that date and the products become read-only.
- New customers. The page says new customers can no longer purchase new Data Center subscriptions after March 30, 2026.
- Existing customers. Existing customers can purchase new subscriptions and subscription expansions until March 30, 2028. They can keep renewing, but the page says renewals cannot extend beyond March 28, 2029.
- Support until then. Through March 28, 2029 Atlassian says it will continue to provide technical support and "Security bug-fixes for critical vulnerabilities" for Data Center products.
- After then. Atlassian says it will offer extended maintenance for certain Data Center customers by exception after March 28, 2029.
- Not covered. The page says Bitbucket and Bamboo Data Center will not end of life.
Three things follow for a 10.3 owner.
- The version clock still runs. The End of Support Policy still lists an end of support date for every Jira line. The commitments on the Data Center page do not move the 10.3 date.
- 11.3 ends before Data Center does. Jira 11.3 reaches its own end-of-life date on December 3, 2027. An installation that stays on Data Center until 2029 passes that date on the way. On the day this guide was published the End of Support Policy listed no Jira line newer than 11.3.
- The other route is Cloud. The Data Center page says that to continue using the impacted products, customers will need to move to cloud. A 10.3 owner who plans to migrate soon still needs a supported line until the migration is done.
Our Atlassian Data Center page tracks those platform dates. Our Atlassian Server and Data Center guide covers the two-year policy across Jira and Confluence and the end of Server support.
One exploited flaw to check before the date
Atlassian's advisory for CVE-2026-21589 says all versions of Jira Software Data Center and Jira Service Management Data Center are affected. It names 10.3.26 as the fixed build on the 10.3 line and 11.3.12 on the 11.3 line, for both products. CISA added the CVE to its Known Exploited Vulnerabilities catalog on October 15, 2026.
A 10.3 installation below 10.3.26 is missing that fix today. Install the fixed build or apply the mitigations in Atlassian's advisory now. Do not wait for the upgrade to 11.3. Our CVE-2026-21589 guide covers the advisory product by product.
What a Jira 10.3 owner should plan
- Check the build you run. If it is below 10.3.26, deal with CVE-2026-21589 first.
- Choose 11.3 as the destination. It is the Long Term Support line with the latest end-of-life date, December 3, 2027. A move to 10.4, 10.5, 10.6 or 10.7 sets up another upgrade within months.
- Read the 11.3 release notes for platform changes. The Jira Software 11.3 release notes say that version runs only on Java 21. Check your Java version, database and Marketplace apps against the release notes and Atlassian's supported platforms page.
- Plan Jira Software and Jira Service Management together. Both 10.3 lines end on the same day and both have 11.3 as the next Long Term Support line.
- Check Confluence too. If you also run Confluence Data Center 9.2, its end-of-life date is December 10, 2026. Our Confluence guide covers it.
- Write down the next two dates. 11.3 ends on December 3, 2027. Atlassian's Data Center end of life is March 28, 2029. Decide between another Data Center upgrade and a move to Cloud before the first of them.
The EOL Checker looks up one product and version. Our Jira Software 10.3 and Jira Service Management 10.3 pages carry the live status and EOL Risk Score.
Frequently Asked Questions
When does Jira 10.3 reach end of life?
December 5, 2026, for Jira Software Data Center 10.3 and for Jira Service Management Data Center 10.3. Atlassian's End of Support Policy lists that day as the end of support (EOS) date of 10.3 for each product. It is two years after 10.3.0 was released, which is the support period the policy sets for every release.
Is Jira 10.3 still supported?
Yes, until December 5, 2026. Atlassian supports each release for two years after its first release, and 10.3 is inside that period for Jira Software Data Center and for Jira Service Management Data Center. Atlassian's policy says it does not provide support for releases that have reached their end of support date.
Is Jira 10.3 an LTS release?
Yes. Atlassian's End of Support Policy labels 10.3 as Long Term Support for Jira Software and for Jira Service Management, and both sets of release notes say 10.3 is a Long Term Support release. Atlassian says a Long Term Support release is supported for the same two years as any other release. What the label adds is bug-fix releases for critical security, stability, data integrity and performance issues until the line reaches end of life.
Which version should I upgrade to from Jira 10.3?
Jira 11.3. On the day this guide was published it was the newest line in Atlassian's End of Support Policy for Jira Software and for Jira Service Management, and Atlassian labels it Long Term Support. Its end-of-life date is December 3, 2027. Lines 10.4 to 10.7 and 11.0 to 11.2 all end earlier, and Atlassian's advisory for CVE-2026-21589 names no fixed build on any of them.
When do Jira 10.4, 10.5, 10.6 and 10.7 reach end of life?
For Jira Software Data Center and for Jira Service Management Data Center: 10.4 on January 22, 2027, 10.5 on March 12, 2027, 10.6 on April 23, 2027 and 10.7 on June 13, 2027. Each is the end of support date in Atlassian's End of Support Policy.
Will Jira 10.3 get security fixes after its end-of-life date?
Atlassian's policies do not commit to any. The Jira Service Management 10.3 release notes promise bug-fix releases until 10.3 reaches end of life. Atlassian's Security Bug Fix Policy says that for a critical vulnerability it issues new bug fix releases for Long Term Support releases that have not reached end of life and for feature versions released within 6 months of the fix. After its end-of-life date 10.3 is in neither group. Atlassian has shipped a build for an older line after that line's date, but nothing commits it to do the same for 10.3.
When does Atlassian Data Center reach end of life?
Atlassian's Data Center end of life page sets end of life for the impacted Data Center products on March 28, 2029, and lists Jira Software Data Center and Jira Service Management Data Center among them. The page says subscriptions expire on that date and the products become read-only. Jira 11.3 reaches its own end-of-life date earlier, on December 3, 2027, so 11.3 does not carry an installation to that date inside Atlassian's support period.
Is Jira 10.3 affected by CVE-2026-21589?
Yes. Atlassian's advisory says all versions of Jira Software Data Center and Jira Service Management Data Center are affected, and names 10.3.26 as the fixed build on the 10.3 line for both. CISA added the CVE to its Known Exploited Vulnerabilities catalog on October 15, 2026. A 10.3 installation below the fixed build should be patched or mitigated now, whatever the end-of-life date.
Related
- Jira Software and Jira Service Management: every line, with live status and EOL Risk Score
- Atlassian Server and Data Center end of life: the two-year policy across Jira and Confluence
- Atlassian CVE-2026-21589: which lines have a fixed build
- Bamboo 10.0 and Jira 10.0: the August 2026 retirements under the same rule
- Confluence end of life and Bitbucket 9.1 end of life: the other Data Center products
- Atlassian Data Center: the platform dates
- EOL Checker and How we verify our dates