End of Support Announcements for JIRA

This page contains announcements of the end of support for various platforms and browsers used with JIRA. These are summarised for upcoming JIRA releases in the table below. Please see the following sections for the full announcements.

End of support matrix for JIRA

The table below summarises the end of support announcements for upcoming JIRA releases. 

Platform/Functionality JIRA end of support
HSQLDB From JIRA 7.0 (announcement)
Oracle JDK 1.7 From JIRA 7.0 (announcement)
Oracle 11G From JIRA 7.0 (announcement)
Internet Explorer 9 From JIRA 7.0 (announcement)
SOAP API (replaced with REST) From JIRA 7.0 (announcement)
Jelly script From JIRA 6.4 (announcement)
WAR download distribution From JIRA 7.0 (announcement)
Microsoft SQL Server 2005 From JIRA 7.0 (announcement)

Why is Atlassian ending support for these platforms?

Atlassian is committed to delivering improvements and bug fixes as fast as possible. We are also committed to providing world class support for all the platforms our customers run our software on. However, as new versions of databases, web browsers, etc, are released, the cost of supporting multiple platforms grows exponentially, making it harder to provide the level of support our customers have come to expect from us. Therefore, we no longer support platform versions marked as end-of-life by the vendor, or very old versions that are no longer widely used.

End of support for HSQLDB

Announced February 2015

Atlassian will end support for HSQLDB (HyperSQL DataBase) in JIRA 7.0. End of support means that Atlassian will not fix bugs in HSQLDB past the support end date.

JIRA ships with a built-in database for evaluation purposes, and currently this is HSQLDB. As of JIRA 7.0, JIRA will ship with H2 (H2 Database Engine) as its built-in database.

HSQLDB (HyperSQL DataBase or HSQLDB) End of Support Notes:

  • JIRA 6.4 will be the last major version of JIRA to officially support HSQLDB (HyperSQL DataBase) for evaluation use.
  • JIRA 6.4.x and earlier versions will continue to work with HSQLDB (HyperSQL DataBase) for evaluation use. However, we will not fix bugs affecting HSQLDB (HyperSQL DataBase) past the support end date.
  • JIRA 7.0 will not be tested with HSQLDB (HyperSQL DataBase).

End of support for Oracle JDK 1.7

Announced February 2015

Atlassian will end support for Java 7 (JRE and JDK 1.7) in JIRA 7.0. End of support means that Atlassian will not fix bugs in Java 7 (JRE and JDK 1.7) past the support end date.

We are ending support for Java 7 (JRE and JDK 1.7), as Oracle Corporation has announced the end of public updates for Java 7: Java SE 7 End of Public Updates Notice.

Java 7 (JRE and JDK 1.7) End of Support Notes:

  • JIRA 6.4 will be the last major version of JIRA to officially support Java 7 (JRE and JDK 1.7).
  • JIRA 6.4.x and earlier versions will continue to work with Java 7 (JRE and JDK 1.7). However, we will not fix bugs affecting Java 7 (JRE and JDK 1.7) past the support end date.
  • JIRA 7.0 will not be tested with Java 7 (JRE and JDK 1.7).
  • Java 8 (JRE and JDK 1.8) is supported, but not bundled with JIRA 6.4

End of support for Oracle 11G

Announced February 2015

Atlassian will end support for Oracle 11G in JIRA 7.0. End of support means Atlassian will not fix bugs related to Oracle 11G past the support end date, except for security-related issues.

We are making this decision as Oracle Corporation have ended support for Oracle 11G as of January 2015. Testing on Oracle 12C will conclude shortly and we'll announce support soon.

Oracle 11G End of Support Notes

  • JIRA 6.4 will be the last major release that supports Oracle 11G
  • JIRA 6.4.x and earlier versions will continue to work on Oracle 11G
  • JIRA 7.0 will not be tested against Oracle 11G

End of support for Internet Explorer 9

Announced February 2015

Atlassian will end support for Internet Explorer 9 in JIRA 7.0. End of support means that Atlassian will not fix bugs related to Internet Explorer 9 past the support end date, except for security-related issues.

We are making this decision to enable us to provide the best user experience to our customers, accelerate our pace of innovation, and give us the ability to utilize modern browser technologies.

Internet Explorer 9 (IE9) End of Support Notes

  • JIRA 6.4 will be the last major release that supports Internet Explorer 9
  • JIRA 6.4.x and earlier versions should continue to work on Internet Explorer 9
  • JIRA 7.0 will not be tested against Internet Explorer 9
  • Internet Explorer 10 and Internet Explorer 11 will continue to be supported in JIRA 7.0.x.

End of support for SOAP

Announced November 2014

Atlassian will end support for SOAP API in JIRA 7.0. The SOAP API's have been replaced by REST API's as Atlassian's recommended and supported remote API.

SOAP End of Support Notes

  • JIRA 6.4 will be the last major release that supports SOAP
  • JIRA 6.4.x and earlier versions should continue to work with SOAP
  • JIRA 7.0 will not include any SOAP API's
  • If you need an alternative that Atlassian supports, the REST API is fully supported by JIRA.

End of support for Jelly Scripts

Announced November 2014

Atlassian will end support for Jelly scripts in JIRA 6.4. If you are using Jelly scripts with JIRA, we suggest you move to Groovy Script Runner or utilise the JIRA Command Line Interface, which will provide you with more flexible options.

Jelly Script End of Support Notes

  • JIRA 6.3 will be the last major release to support Jelly scripts
  • JIRA 6.3.x and earlier versions should continue to work fine with Jelly scripts
  • JIRA 6.4 will not include Jelly.
  • If you need an alternative to Jelly scripts, Groovy Script Runner or the JIRA Command Line Interface are the suggested alternatives that work with JIRA.

End of support for WAR distribution

Announced August 2014
Atlassian will stop releasing the WAR distribution of JIRA in JIRA 7.0.

Why are we ending support for this?

  • We are trying to reduce the amount of combinations and confusion around this for customers downloading a Server (BTF) edition
  • The WAR edition is a bit more complex to install and gets more difficult as the installation ages and gets bigger - we want to reduce that complexity
  • We can't and don't test every permutation of environments + app servers that a customer might deploy into, nor can we control what else might be in that environment, which can lead to a poor user experience
  • We only support Tomcat - JIRA doesn't work on WLS or WebSphere anyways, other app servers - maybe.

Anything we release, we want to make sure users get a good experience in installation and usage and don't have to deal with app server quirks etc.

End of support for Microsoft SQL Server 2005

Announced June 2014

Atlassian will end support for Microsoft SQL Server 2005 in JIRA 7.0. End of support means that Atlassian will not fix bugs related to Microsoft SQL Server 2005 past the support end date.

We are making this decision in order to reduce our database testing and support, and help us speed up our ability to deliver market-driven features. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

Microsoft SQL Server 2005 End of Support Notes:

  • JIRA 6.4 will be the last major version of JIRA to officially support Microsoft SQL Server 2005.
  • JIRA 6.4.x and earlier versions should continue to work with Microsoft SQL Server 2005.
  • JIRA 7.0 will not be tested against Microsoft SQL Server 2005.
  • Microsoft SQL Server 2008 and 2008 R2 will continue to be supported in JIRA 7.0.x (see Supported Platforms).
  • We will start supporting Microsoft SQL Server 2012 in JIRA 6.4. 

Older announcements

  Click here to expand...

On this page (most recent announcements first):

End of support for PostgreSQL 8.3.x

Announced June 2014

Atlassian will end support for PostgreSQL 8.3.x in JIRA 6.3. We are planning on releasing JIRA 6.3 in mid-2014. End of support means that Atlassian will not fix bugs related to PostgreSQL 8.3.x past the support end date.

We are making this decision, as the PostgreSQL Global Development Group has already ended support for PostgreSQL 8.3 (in February 2013). If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

PostgreSQL 8.3.x End of Support Notes:

  • JIRA 6.2 will be the last major version of JIRA to officially support PostgreSQL 8.3.x.
  • JIRA 6.2.x and earlier versions should continue to work with PostgreSQL 8.3.x.
  • JIRA 6.3 will not be tested against PostgreSQL 8.3.x.
  • PostgresSQL 8.4 and 9.0 will continue to be supported in JIRA 6.3.x (see Supported Platforms).
  • We will start supporting PostgreSQL 9.1, 9.2 and 9.3 in JIRA 6.3. 

End of support for Internet Explorer 8

Announced October 2013

Atlassian will end support for Internet Explorer 8 in JIRA 6.3. We are planning on releasing JIRA 6.3 in mid-2014. End of support means that Atlassian will not fix bugs related to Internet Explorer 8 past the support end date, except for security-related issues.

We are making this decision to enable us to provide the best user experience to our customers, accelerate our pace of innovation, and give us the ability to utilize modern browser technologies. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

Internet Explorer 8 End of Support Notes:

  • JIRA 6.2 will be the last major version of JIRA to officially support Internet Explorer 8.
  • JIRA 6.2.x and earlier versions should continue to work with Internet Explorer 8.
  • JIRA 6.3 will not be tested against Internet Explorer 8.
  • Internet Explorer 9 and 10 will continue to be supported in JIRA 6.3.x (see Supported Platforms).

Deprecated plugins for JIRA (01 August 2013)

This section announces the end of Atlassian support for the Voters and Watchers and Labels plugins. Atlassian will not fix bugs related to either the "Voters and Watchers" or the "Labels" plugins past the support end date. Note, these plugins are not bundled with JIRA. In case of both of these plugins, the respective functionality has been largely replaced as part of the JIRA core since version 4.2 (Voters and Watchers) and 4.1 (Labels).

We will stop supporting the following plugins:

  • From JIRA 6.1, due in the second half of 2013, JIRA will no longer support the "Voters and Watchers" or the "Labels" plugins.

We made this decision in order to reduce our plugin support, to reduce testing time and help us speed up our ability to deliver market-driven features. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

"Voters and Watchers" and "Labels" plugins End of Support Notes:

  • JIRA 6.0 will be the last major version of JIRA to officially support the "Voters and Watchers" and "Labels" plugins.
  • JIRA 6.0.x and earlier versions should continue to work with the "Voters and Watchers" and "Labels" plugins.
  • JIRA 6.1 will not be tested with the "Voters and Watchers" and "Labels" plugins.

Deprecated source control systems for JIRA (8 July 2013)

This section announces the end of Atlassian support for CVS/ViewCVS. At the support end date, all functionality related to CVS/ViewCVS integration will be removed from JIRA. Also, Atlassian will not fix bugs related to CVS/ViewCVS integration past the support end date. Note, this feature was never available in JIRA Cloud.

We will stop supporting the following source control system:

  • From JIRA 6.1, due in the second half of 2013, JIRA will no longer include nor support CVS/ViewCVS integration.

We made this decision in order to reduce our source control system support, to reduce testing time and help us speed up our ability to deliver market-driven features. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

CVS/ViewCVS End of Support Notes:

  • JIRA 6.0 will be the last major version of JIRA to officially include and support CVS integration.
  • JIRA 6.0.x and earlier versions should continue to work with CVS/ViewCVS.
  • CVS/ViewCVS integration is available as an unsupported open source plugin for JIRA 6.1.x and later: https://bitbucket.org/atlassian/jira-cvs-plugin/overview
  • The JIRA CVS plugin has been created from the JIRA source code, so JIRA 6.1.x and later should work with CVS/ViewCVS without any additional setup.
  • JIRA 6.1 will not be tested with CVS/ViewCVS.
  • If you need an alternative that is supported by Atlassian, Atlassian's FishEye integrates with JIRA and supports CVS repository access.

End of support for characters other than letters, numbers and the underscore in JIRA's project key (13 May 2013, updated 6 August 2013)

This section announces the end of support for characters other than letters, numbers and the underscore in JIRA's project key in downloadable JIRA. Note, project key configuration was never allowed in JIRA Cloud. 

From JIRA 6.1, due in the second half of 2013, we will only support customized project keys that meet all of the conditions specified below:

  • Only letters, numbers or the underscore character can be used.
  • The first character must be a letter from the Modern Roman Alphabet. All other letter characters in the key must also be from the Modern Roman Alphabet.
  • The first and all other letter characters must be in upper case.

Examples of supported keys: PRODUCT_2013; R2D2; MY_EXAMPLE_PROJECT.  
Examples of unsupported keys: 2013PROJECT (first character is not a letter); PRODUCT-2012 (hyphens are not supported).

We understand that some customers may be in the position where their current project keys do not meet the above requirements. We want to help these customers migrate to a supported format. To do this, we will implement the highly-voted feature request: Editing Project Keys (JRA-2703). We have started work on this and should complete it for the JIRA 6.1 release. Please note, we will continue to provide the same level of support for your current customized project keys until this feature has been implemented. 

Why are you only supporting letters, numbers and the underscore character for customized project keys?

We are only supporting letters, numbers and the underscore character, as supporting every possible character for customized project keys is a challenging task for JIRA plugins, integration with other Atlassian products, as well as core JIRA functionality. Hence, we will only be supporting the most commonly used characters. From your feedback and our research, letters and numbers are commonly used for customized project keys. Also, the underscore is by far the most commonly used separator character, with hyphens a distant second. However, we will not be supporting hyphens as they interfere with the separator that JIRA uses for issue numbers.

End of support notes:

  • Please note that our previous announcement for the end of project key format configuration in JIRA 6.0 no longer applies. This is largely due to the great feedback provided by you, our customers.
  • In JIRA 6.0, we will continue to support customized project keys, however we recommend that customers only use customized project keys if they meet the conditions specified above.
  • Classic Boards in JIRA Agile are not compatible with the supported project key format noted above. You must use the default project key format. If you are not using the Classic Boards, you can change to a supported project key format.

Deprecated Java platforms for JIRA (18 January 2013)

This section announces the end of Atlassian support for Java 6 (JRE and JDK 1.6). End of support means that Atlassian will not fix bugs in Java 6 (JRE and JDK 1.6) past the support end date.

We will stop supporting the following Java platform:

  • From JIRA 6.0, due towards the middle of 2013, JIRA will no longer support Java 6 (JRE and JDK 1.6).

We are ending support for Java 6 (JRE and JDK 1.6), as Oracle has announced the end of public updates for Java 6: Java SE 6 End of Public Updates Notice. We are committed to helping our customers understand this decision and to assist you in upgrading JIRA, (we recommend the JIRA Installer for the upcoming 6.0 release, which will bundle its own Java 7 environment).

Please refer to the   Supported Platforms for more details regarding platform support for JIRA. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

Java 6 (JRE and JDK 1.6) End of Support Notes:

  • JIRA 5.2 will be the last major version of JIRA to officially support Java 6 (JRE and JDK 1.6).
  • JIRA 5.2.x and earlier versions will continue to work with Java 6 (JRE and JDK 1.6). However, we will not fix bugs affecting Java 6 (JRE and JDK 1.6) past the support end date.
  • JIRA 6.0 will not be tested with Java 6 (JRE and JDK 1.6).

End of support for project key format configuration (22 November 2012)

This announcement no longer applies. Please see   this announcement regarding project key format customization instead.

This section announces the end of Atlassian support for project key format configuration in downloadable JIRA (note, project key configuration was never allowed in JIRA Cloud). End of support means that Atlassian will not fix bugs (past the support end date) that occur due to customization of the project key.

  • From JIRA 6.0, due in the first half of 2013, JIRA will no longer support project key format configuration.

We are ending support for project key format configuration, as changing the product key format will break JIRA plugins, integration with other Atlassian products, as well as core JIRA functionality. We are committed to helping our customers understand this decision and guiding them back to use the standard project key format.

Deprecated application servers for JIRA (27 August 2012)

This section announces the end of Atlassian support for Tomcat 5.5.x for JIRA WAR. End of support means that Atlassian will not fix bugs in certain application servers past the support end date.

We will stop supporting the following application servers:

  • From JIRA 5.2, due towards the end of 2012, JIRA will no longer support Tomcat 5.5.x.

We are ending support for Tomcat 5.5, as the Apache Tomcat team has announced the end of life (EoL) for version 5.5 as the 30th September 2012 (see announcement). We are committed to helping our customers understand this decision and assisting them in migrating to Tomcat 6.0.32 or later, if needed. Please refer to the Supported Platforms for more details regarding platform support for JIRA. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

Tomcat 5.5.x End of Support Notes:

  • JIRA 5.1 will be the last major version of JIRA to officially support Tomcat 5.5.x.
  • Tomcat 6.0.32 will be supported in JIRA 5.2. We are planning on adding support for Tomcat 7.0.29 in JIRA 5.2.
  • JIRA 5.1.x and earlier versions will continue to work with Tomcat 5.5.x. However, we will not fix bugs affecting Tomcat 5.5.x past the support end date.
  • JIRA 5.2 will not be tested with Tomcat 5.5.x.

Deprecated databases for JIRA (24 July 2012)

 

This section announces the end of Atlassian support for certain database versions for JIRA. End of support means that Atlassian will not fix bugs related to certain database versions past the support end date.

We will stop supporting the following database versions:

  • From JIRA 5.2, due towards the end of 2012, JIRA will no longer support Postgres 8.2.

We are ending support for Postgres 8.2, as the PostgreSQL Global Development Group has already announced that the end of life (EoL) for version 8.2. We are committed to helping our customers understand this decision and to assist you in migrating to a different database, if needed. Please refer to the Supported Platforms for more details regarding platform support for JIRA. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

PostgreSQL End of Support Notes:

  • The PostgreSQL Global Development Group's support for PostgreSQL 8.2 ended on December 2011 (see the PostgreSQL versioning policy).
  • JIRA 5.1 will be the last major version of JIRA to officially support PostgreSQL 8.2.
  • PostgreSQL 8.3 and 8.4 will be supported in JIRA 5.2.
  • JIRA 5.1.x and earlier versions will continue to work with PostgreSQL 8.2. However, we will not fix bugs affecting PostgreSQL 8.2 past the support end date.
  • JIRA 5.2 will not be tested with PostgreSQL 8.2.

Deprecated web browsers for JIRA (6 April 2011)

 

This section announces the end of Atlassian support for certain web browsers for JIRA.

We will be ending support for older versions of web browsers as follows:

  • JIRA 4.4.x will be the last versions of JIRA to support Internet Explorer 7.

The details are below. Please refer to the Supported Platforms for more details regarding platform support for JIRA. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

Internet Explorer 7 End of Support Notes:

  • IE7, now 4+ years after its release, has less than 10% of browser market share. Microsoft has released IE8 and recently IE9.
  • JIRA 4.4 (due mid 2011) will be the last major version of JIRA to officially support Internet Explorer 7.
  • JIRA 4.4.x and earlier versions will continue to work with Internet Explorer 7. However, we will not fix bugs affecting this browser version past the last version of JIRA 4.4.x to be released.

Deprecated databases for JIRA (6 April 2011)

 

This section announces the end of Atlassian support for certain databases for JIRA.

We will be ending support for older versions of databases as follows:

  • JIRA 4.4.x will be the last versions of JIRA to support Oracle 10.1, Oracle 10.2 and MySQL 5.0.

The details are below. Please refer to the Supported Platforms for more details regarding platform support for JIRA. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

Oracle 10.1 & 10.2 End of Support Notes:

  • Oracle Premier support for 10.2 ended on July 31, 2010.
  • JIRA 4.4 (due mid 2011) will be the last major version of JIRA to officially support Oracle 10.1 and Oracle 10.2.
  • JIRA 4.4.x and earlier versions will continue to work with Oracle 10.1 and Oracle 10.2. However, we will not fix bugs affecting Oracle 10.1 and Oracle 10.2 past the last version of JIRA 4.4.x to be released.

MySQL 5.0 End of Support Notes:

  • MySQL support for MySQL 5.0 ended on December 31, 2009 (http://www.mysql.com/support/eol-notice.html).
  • JIRA 4.4 (due mid 2011) will be the last major version of JIRA to officially support MySQL 5.0.
  • JIRA 4.4.x and earlier versions will continue to work with MySQL 5.0. However, we will not fix bugs affecting MySQL 5.0 past the last version of JIRA 4.4.x to be released.

Deprecated web browsers for JIRA (27 September 2010)

This section announces the end of Atlassian support for certain web browsers for JIRA.

We will stop supporting older versions of web browsers as follows:

  • From JIRA 4.3, due in Quarter 1 2011, JIRA will no longer support Safari 4 and Firefox 3.0.x.

The details are below. Please refer to the Supported Platforms for more details regarding platform support for JIRA. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

End of Life Announcement for Web Browser Support

Web Browsers

Support End Date

Safari 4

When JIRA 4.3 releases (due in Quarter 1 2011)

Firefox 3.0.x

When JIRA 4.3 releases (due in Quarter 1 2011)

  • General End of Support Notes:
    • JIRA 4.2 (due Quarter 4 2010) will be the last JIRA version to officially support Safari 4 and Firefox 3.0.x.
    • 'Support End Date' means that JIRA 4.2 and previous released versions will continue to work with Safari 4 and Firefox 3.0.x. However, we will not fix bugs affecting these browser versions past the support end date.
  • Firefox End of Support Notes:
    • The decision to end support for Firefox 3.0.x in JIRA 4.3 was made in line with Mozilla's support strategy, which indicates that Firefox 3.0.x will be maintained with security and stability updates until January 2010.

Deprecated databases for JIRA (13 August 2010)

This section confirms that Atlassian support for DB2 for JIRA ended in JIRA 4.0. End of support means that Atlassian will no longer fix bugs related to DB2.

We do not support the following databases:

  • Atlassian ended support for DB2 at the release of JIRA 4.0 (October 2009), with the final support for these platforms in JIRA 3.13.

We made this decision in order to reduce our database support, to reduce testing time and help us speed up our ability to deliver market-driven features. We are committed to helping our customers understand this decision and assist them in migrating to a supported database, if needed.

Please refer to the Supported Platforms for more details regarding platform support for JIRA. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

  • DB2 End of Support Notes:
    • 'Support End Date' means that JIRA 3.13 and versions prior to JIRA 3.13 will continue to work with the DB2. However, we will not fix bugs affecting DB2 past the support end date.
    • JIRA 4.0 (released in October 2009) and later versions of JIRA have not been tested with DB2.

Deprecated application servers for JIRA (27 January 2010)

This section announces the end of Atlassian support for certain application server platforms for JIRA WAR/EAR. End of support means that Atlassian will not fix bugs in certain application servers past the support end date.

We will stop supporting the following application servers:

  • From JIRA 4.1, due late Q1 2010, JIRA will no longer support JBoss application servers.
  • From JIRA 4.2, due in Q3 2010, JIRA will no longer support Oracle WebLogic or IBM WebSphere.

We are reducing our application server platform support to reduce the amount of testing time and help us speed up our ability to deliver market-driven features. We are committed to helping our customers understand this decision and assisting them in migrating to Tomcat, our supported Application Server.  You have the option of installing the JIRA Standalone version which includes our supported Tomcat application server. For instructions, please see Switching Application Servers to Apache Tomcat.

Please refer to the Supported Platforms for more details regarding platform support for JIRA. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

End of Life Announcement for Application Server Support

Application Servers

Support End Date

JBoss 4.2.2

When JIRA 4.1 releases, due late Q1 2010

Oracle WebLogic 9.2

When JIRA 4.2 releases, due Q3 2010

IBM WebSphere 6.1

When JIRA 4.2 releases, due Q3 2010

  • JBoss End of Support Notes:
    • 'Support End Date' means that JIRA 4.0 and previous released versions will continue to work with JBoss Application Servers. However, we will not fix bugs affecting JBoss application servers.
    • JIRA 4.1 will not support JBoss application servers.
  • WebSphere and WebLogic End of Support Notes:
    • Atlassian is targeting a support end of life for Oracle WebLogic and IBM WebSphere in Q3 2010, with the final support for these platforms in JIRA 4.1.
    • 'Support End Date' means that JIRA 4.1 and previous released versions will continue to work with the stated application servers. However, we will not fix bugs affecting Oracle WebLogic and IBM WebSphere application servers past the support end date.
    • JIRA 4.2 (due to release in Q3 2010) will only be tested with and support Tomcat 5.5 and 6.0.
    • If you have concerns with this end of support announcement, please email eol-announcement at atlassian dot com.

Why is Atlassian doing this?

Atlassian is committed to delivering improvements and bug fixes as fast as possible. We are also committed to providing world class support for all the platforms our customers run our software on. However, as the complexity of our applications grows, the cost of supporting multiple platforms increases exponentially. Each new feature has to be tested on several combinations of application servers, with setup and ongoing maintenance of automated tests. At times, 30% of the development team is busy coding solutions for edge cases in various application servers. Moving forward, we want to reduce the time spent there in order to increase JIRA development speed significantly.

We have chosen to standardise on Tomcat, because it is the most widely used application server in our user population. It is fast, robust, secure, well-documented, easy to operate, open source, and has a huge community driving improvements. It is the de facto industry standard, with several companies available that specialise in providing enterprise grade support contracts for it, ranging from customizations to 24/7 support.

Deprecated Java platforms for JIRA (27 January 2010)

This section announces the end of Atlassian support for certain Java Platforms for JIRA.

We will stop supporting the following Java Platforms:

  • From JIRA 4.2, due Q3 2010, support for Java Platform 5 (JDK/JRE 1.5) will end.

We are ending support for Java Platform 5, in line with Sun's Java SE Support Road Map (i.e. "End of Service Life" for Java Platform 5 dated October 30, 2009). We are committed to helping our customers understand this decision and assisting them in updating to Java Platform 6, our supported Java Platform.

The details are below. Please refer to the Supported Platforms for more details regarding platform support for JIRA. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

End of Life Announcement for Java Platform Support

Java Platform

Support End Date

Java Platform 5 (JDK/JRE 1.5)

When JIRA 4.2 releases, due Q3 2010

  • Java Platform 5 End of Support Notes:
    • Atlassian intends to end support for Java Platform 5 in Q3 2010.
    • 'Support End Date' means that JIRA 4.1.x and previous released versions will continue to work with Java Platform 5 (JDK/JRE 1.5). However, we will not fix bugs related to Java Platform 5 past the support end date.
    • JIRA 4.2 (due to release in Q3 2010) will only be tested with and support Java Platform 6 (JDK/JRE 1.6).
    • If you have concerns with this end of support announcement, please email eol-announcement at atlassian dot com.

Deprecated web browsers for JIRA (11 December 2009)

This section announces the end of Atlassian support for certain web browsers for JIRA.

We will stop supporting older versions of web browsers as follows:

  • JIRA 4.1 will be the last version of JIRA to support IE6. (From JIRA 4.0 to JIRA 4.1, all of the main functionality will work in IE 6. However, some of the visual effects will be missing.)

The details are below. Please refer to the Supported Platforms for more details regarding platform support for JIRA. If you have questions or concerns regarding this announcement, please email eol-announcement at atlassian dot com.

End of Life Announcement for Web Browser Support

Web Browsers

Support End Date

Internet Explorer 6

When JIRA 4.2 releases (target Q3 2010)

  • Internet Explorer 6 End of Support Notes:
    • JIRA 4.1 (due late Q1 2010) will be the last version to officially support Internet Explorer 6.
    • JIRA 4.2 is currently targeted to release Q3 2010 and will not support IE6.
    • This decision was made in line with Microsoft's Support Lifecycle policy, which indicates the official end of support for Internet Explorer 6 on 13th July, 2010. Please note that released versions of JIRA up to and including JIRA 4.1 will continue working with IE6 just as they did before, but we will not fix bugs affecting Internet Explorer 6.
    • You may be able to use Internet Explorer 6 for the most common use cases like viewing and editing content in JIRA 4.1 and earlier, but official support for this browser will end once you upgrade to JIRA 4.2.

Was this helpful?

Thanks for your feedback!

51 Archived comments

  1. User avatar

    Kavian Moradhassel

    If project key configuration will no longer be supported, can you describe what the required format will be?

    Note that this functionality is used in other ways than just allowing non-standard characters (which I assume is what you're trying to avoid?)...we have two instances used in our company, and we use project key configuration to enforce a naming convention that keeps the project keys unique across the instances.

    22 Nov 2012
    1. User avatar

      Roy Krishna [Atlassian]

      The standard JIRA project key configuration requires two or more uppercase alphabetical characters — based on the regular expression ([A-Z][A-Z]+).

      22 Nov 2012
  2. User avatar

    Markus Lepper

    Hello Roy,

    does that mean project keys like "AB1C" are not allowed anymore? Or could we still have ([A-Z][A-Z, 0-9]+)?

    BR, Markus

    24 Nov 2012
    1. User avatar

      Roy Krishna [Atlassian]

      Yes, it means that customising the project key pattern will not be supported. However you can still change it to include numbers if you want to.

      25 Nov 2012
      1. User avatar

        Matt Doar (ServiceRocket)

        Roy,

        That's confusing. So changing the project key pattern will no longer be allowed, correct? The default project key pattern does not allow numbers just letters, as far as I am aware. 

        Also, do you have some details of how are you proposing to change an existing project key in a JIRA instance? I can imagine moving issues to a new project, global replace in an XML backup, SQL scripts to change the project key, ...

        ~Matt

        26 Nov 2012
        1. User avatar

          Roy Krishna [Atlassian]

          Matt,

          Changing the project key will be 'allowed' but not supported and customers can still change the project key format the way they have always done.

          Not supported means that if things break in JIRA because customers are using non supported characters then those issues will not be fixed. 

          I hope that clears things up.

          26 Nov 2012
          1. User avatar

            Matt Doar (ServiceRocket)

            That does, thanks. Perhaps the original text at the top needs that info too?

            27 Nov 2012
          1. User avatar

            Anonymous

            That means we will be scrapping our testing efforts and move on to other products that do not force us to use arbitrarily constrained project keys that are not useful in any way for us. - But at least we did just waste some time...

            12 Dec 2012
            1. User avatar

              Roy Krishna [Atlassian]

              Hi there,

              I'd love to chat to you some more about this, however I don't have any way to contact you. Feel free to contact me at roy at atlassian dot com

              12 Dec 2012
          1. User avatar

            Anonymous

            Hi Roy,

            I saw there is a nice piece of discussion about this on Atlassian Answers.. Could you please refer to this topic and let us in a little bit more details how this problem will be handled in the future?

            Thanks!

             

            09 Jan 2013
  3. User avatar

    Anonymous

    Having some sort of non-letter separator in project keys makes them easier to read and manage. That's why a number of deployments have customized the key pattern to allow underscores. Disallowing (or not supporting) that would affect a large number of end-users.

    I think I understand the tradeoffs - it would certainly save some effort for Atlassian and third party developers if they don't have to quote issue IDs in SQL queries (presumably, this is why underscores are shunned - per https://jira.atlassian.com/browse/JRA-27967, https://ecosystem.atlassian.net/browse/STRM-2095). But I still wonder whether Atlassian is setting priorities correctly here.

    04 Feb 2013
    1. User avatar

      Anonymous

      For me, the priorities are definitely NOT set correctly here. At least support for numbers is ESSENTIAL to setting up project space.
      We have several different machine types, not surprisingly identified by some alphanumeric expression (T6000, T8000, Txxx..).

      How can you reflect such a concept to project keys with only characters in a meaningful manner? You can't, it will creat crappy and ugly
      ticket keys...

      13 Feb 2013
  4. User avatar

    Broadcom Support

    We have over 900 projects that use product reference number as the project name/key.   We know it is a problem with Fisheye/Crucible but will it break Confluence/Stash/Bamboo ?

    12 Mar 2013
  5. User avatar

    Darshak Thakore

    If alphanumeric keys are not allowed, we will have no choice but to abandon Jira.

    We've been an ardent Atlassian products users for a number of years now (Jira, Confluence, Fisheye, Crucible, Bamboo) and i'm actually saddened to see that over the years Atlassian is becoming more and more like Microsoft. "They know what's best for the customer because they want to give (their) best experience to the customer" 

    I hope that you not only listen to your customers on this one but actually do something in time.

     

    21 Mar 2013
    1. User avatar

      Marcel Trautwein alias childno͡.de

      have you read the notification above?

       

      … we are investigating re-introducing support for project keys with different configurations than just letters, specifically looking at numbers and potentially underscores as well and the impact they have on Atlassian and third party plugins. … We'll have an update before JIRA 6.0 ships.

       

       

      so I think: yes, they did hear the crowd... keep cool.. i bet there'll be a solution and no....they are really not like Microsoft but you're right: I'm also not happy about some product cycles / "feature" but you are empowered to improve it yourself with plugins while the base license is still "cheap" compared to other competitiors.. but nevvertheless..

      Tip: (but something you should know as a long term customer): Better than denouncing and complaining about something in a wiki comment, is to vote for the right JIRA issue! (wink)

      21 Mar 2013
  6. User avatar

    Denis Cabasson

    +1 on the fact that project keys should be able to have more than letters. Numbers would definitely be nice. Our configuration is currently [A-Z]{2}[A-Z0-9]* so that it always starts with letters, but then can be followed by numbers, because some of our projects include a year in them.

    15 Apr 2013
  7. User avatar

    Matt Doar (ServiceRocket)

    Are there any length restrictions on the new key format (with numbers)?

    13 May 2013
    1. User avatar

      Andrew Lui [Atlassian Technical Writer]

      Hi Matt,

      The existing key length restriction of 255 characters should not change with the new key format.

      Kind Regards,
      Andrew

      15 May 2013
      1. User avatar

        Matt Doar (ServiceRocket)

        Thanks. I admit I've never seen a project key longer than about 20 characters but I bet there are some out there. Just for typing practice.

        15 May 2013
      1. User avatar

        MarkW

        This is good info to know. I didn't see it anywhere but our users was concerned with this.

        15 May 2013
  8. User avatar

    Broadcom Support

    What do you mean by labels watchers and votes.  Do you mean this functionally has been incorporated or is no longer a part of JIRA?

    01 Aug 2013
    1. User avatar

      Andrew Lui [Atlassian Technical Writer]

      Hi,

      The functionality from the "Voters and Watchers" and "Labels" plugins have been incorporated into core JIRA.

      Kind Regards,
      Andrew

      01 Aug 2013
  9. User avatar

    Daniel Lai

    The page Configuring Project Keys still mentions that GreenHopper and Bamboo only support the default project key format in Jira. Is this statement still true no matter what version of JIRA is used and even if a custom project key format adheres to the guidelines that are supported in JIRA 6.1? The above announcement does mention that for 6.1, the supported project key formats are being restricted due in part to problems with "integration with other Atlassian products", so if we follow the supported guidelines, I would think this would be supported in GreenHopper/Bamboo as well. But the blanket statement at Configuring Project Keys contradicts this, and I'm wondering if that statement needs to be revised. 

    We are on JIRA 5.2.5 and GreenHopper 6.2 and want to allow numbers and possibly underscore in the project key (after the first character). It's not clear if there are going to be any problems in GreenHopper doing this. Or do we need to wait till we're on JIRA 6.1 and then a supported custom project key format will also be supported in GreenHopper, and if so, what version of GreenHopper would we need to be on? Can anyone from Atlassian please clarify this?

    21 Aug 2013
  10. User avatar

    John Campbell

    If you are using OnDemand and want to change your key format to something other than just letters, please vote here for this feature.  Even if you are not OnDemand, please help.

    JRA-37162 - Allow numerical numbers in project Keys for OnDemand Closed

    05 Dec 2013
  11. User avatar

    Matt Doar [ServiceRocket]

    Thanks for the clear communication about the changes. This will help our customers plan for the upcoming EOLs

    04 Jun 2014
  12. User avatar

    Derek Sheeman

    I don't think you guys realize just how much IE8 is still in use by corporate america ...

    14 Aug 2014
    1. User avatar

      Matt Doar [ServiceRocket]

      So is COBOL.

      14 Aug 2014
      1. User avatar

        Derek Sheeman

        True, but I don't think JIRA ever ran on COBOL. (smile)

        15 Aug 2014
    1. User avatar

      Tim Eddelbuettel

      Not only in america, also in germany.

      15 Aug 2014
    1. User avatar

      Karen Mort

      And Australia!

      12 Feb 2015
  13. User avatar

    Tim Eddelbuettel

    Atlassian will stop releasing the WAR distribution of JIRA in JIRA 7.0.

     

    Why you stop the WAR distibution? That means you only support the standalone installation method with your bundled tomcat configuration?

    27 Aug 2014
    1. User avatar

      Matt Doar [ServiceRocket]

      I'd be interested to see a reason too, so I can explain to the few customers who do use it. Actually, I suspect that's why it's being discontinued - because so few people deploy JIRA using a WAR

      27 Aug 2014
      1. User avatar

        Marty Henderson [Atlassian]

        Hi folks,

        There are a couple of main reasons that we are discontinuing support for the WAR distro.

        • We are trying to reduce the amount of combinations and confusion around this for customers downloading a BTF edition
        • The WAR edition is a bit more complex to install and gets more difficult as the installation ages and gets bigger - we want to reduce that complexity
        • We can't and don't test every permutation of environments + app servers that a customer might deploy into, nor can we control what else might be in that environment, which can lead to a poor user experience
        • We only support Tomcat - JIRA doesn't work on WLS or WebSphere anyways, other app servers - maybe.

        Anything we release, we want to make sure users get a good experience in installation and usage and don't have to deal with app server quirks etc.

        Hope this makes sense folks.

        27 Aug 2014
        1. User avatar

          Matt Doar [ServiceRocket]

          Marty,

          Thanks that is helpful. Please would you add it to the section at Re: End of Support Announcements for JIRA

          (I have edit permission but am not supposed to touch release notes etc)

          27 Aug 2014
          1. User avatar

            Marty Henderson [Atlassian]

            Done! (smile)

            27 Aug 2014
            1. User avatar

              Matt Doar [ServiceRocket]

              Thanks! BTW, BTF = Server I assume

              27 Aug 2014
              1. User avatar

                Marty Henderson [Atlassian]

                Yep - I'm still making the mental transition.

                27 Aug 2014
        1. User avatar

          It Team

          This is bad!

          Amount of combinations and confusions? Sorry but s.o. who can't deal with the existing few number of combinations will be over challenged with operating a nontrivial product like JIRA anyway.

          WAR edition more complex? So what, nobody is forced to use it.

          Only support tomcat? Even for Tomcat, WAR edition has many advantages.

          We ship our optimized unified tomcat configuration with defined port ranges, multi instance support and production ready features like firewall-enabled JMX access and adjusted logging. Installing the WAR distribution is far more efficient for us than adjusting the standalone distribution accordingly for each update.

          17 Oct 2014
  14. User avatar

    Matt Doar [ServiceRocket]

    Warren, you added: "If you need an alternative that Atlassian supports, Groovy Script Runner is fully supported by JIRA.".

    Is this a new thing?https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner says that "Jamie Echlin supports Script Runner. You can ask a support question via Atlassian Answers to get help."

    10 Nov 2014
    1. User avatar

      Warren Thompson

      You're quite right Matt Doar [ServiceRocket], the intention was to communicate that JIRA will work with Groovy script runner, not that Atlassian support it as one of our own products.

      I'll amend the text asap to make it clear.

      Thanks,

      Warren

      11 Nov 2014
  15. User avatar

    Marcel Trautwein alias childno͡.de

    Oracle 12C will be supported in JIRA 6.4.

     

    Time to update Supported Platforms!

    12 Feb 2015
  16. User avatar

    Matthew Smith

    • JIRA 6.3 will be the last major version of JIRA to officially support Microsoft SQL Server 2005.
    • JIRA 6.3.x and earlier versions should continue to work with Microsoft SQL Server 2005.
    • JIRA 7.0 will not be tested against Microsoft SQL Server 2005.

    The above implies that JIRA 6.4 will not support SQL Server 2005, but will be tested against it. Which doesn't quite make sense - can you clarify the support status of SQL Server 2005 in 6.4?

    26 Feb 2015
    1. User avatar

      Warren Thompson

      Hi Matthew Smith,

      The statement isn't quite correct, it should read JIRA 6.4 will not be tested against Microsoft SQL Server 2005. I'll correct it now. We won't be testing against any version of JIRA  from JIRA 6.4 onwards.

      Thanks,

      Warren

      27 Feb 2015
      1. User avatar

        Matthew Smith

        Hi Warren,
        There is still a slight inconsistency between this:
        • JIRA 6.3 will be the last major version of JIRA to officially support Microsoft SQL Server 2005.

        and the Supported Platforms page for JIRA 6.4, which does list SQL Server 2005 as a supported platform:

        Could you please clarify the status of SQL Server 2005 support in 6.4 once and for all?!

        14 Apr 2015
        1. User avatar

          Warren Thompson

          Hi Matthew Smith,

          Apologies for the confusion. I've corrected the page now. The correct statement is that JIRA 6.4 is tested against, and supports, SQL Server 2005. Our 7.0 release will not support SQL Server 2005.

          Again, apologies for the confusion, and thank you for pointing it out. We've made some changes to our roadmap for supported platforms, and I've also reviewed this page to make sure all the content is current and correct.

          Thanks,

          Warren

          15 Apr 2015
  17. User avatar

    Aggelos Paraskevopoulos [Cententia]

    Oracle extended support for 11G R2 until end of 2018. Discontinuing support as early as JIRA 7 seems a bit aggressive?

    Oracle 11g Release 2 was desupported on 31 January 2015 and extended support will end on 31 January 2018.

    Cheers,

    Aggelos

    19 Mar 2015
    1. User avatar

      Otto Ruettinger

      Hi Aggelos Paraskevopoulos [Cententia],

      We made this decision due to the standard support being EOL'ed in Jan2015 and the fact that not all customers sign up for extended support.

      We need to balance the amount of technical debt we carry to maintain all of our platforms. The more efficient we are at doing this the more resource we have to expend on product improvements and new features that our customers love.

      I realise that this will not fit every customer and we're constantly assessing this balance.

       

      Thanks,

      Otto Ruettinger, Principal Product Manager, JIRA

      19 Mar 2015
  18. User avatar

    Francois M. FASBENDER

    New releases of JIRA not compatible with IE9.0 or IE8.0...  Just incredible....

    It means that big companies like mine should stop to upgrade JIRA?? (I don't see how to convince CIO to upgrade 1000+ boxes running on IE 8.0... 9.0. just to be able to upgrade JIRA)...

    It means that we should pay an increasingly huge maintenance fee just to get a 'support' on old releases?

    So in this case, no other choice than stopping the maintenance fee for several years...

     

     

    20 Apr 2015
    1. User avatar

      Philip Schlesinger

      Your company has 1000+ boxes running an IE version less than IE11?  Is your CIO aware that after January 2016, only IE 11 will receive support patches for vulnerabilities?  

      Does your CIO prefer to run vulnerable systems?  If not, he/she had better get an upgrade plan in place ASAP – with a project budget that I would bet will be far more pricey than a little Atlassian support agreement fee...

      30 Apr 2015
      1. User avatar

        Darren Pegg

        I would be more than happy if JIRA/Confluence could actually be fully compatible with IE11 by then or somewhat closer to 99%

        15 Jul 2015
        1. User avatar

          Philip Schlesinger

          Hi Darren,

          What incompatibilities do you still see between the most recent JIRA release and IE 11?  Atlassian says that IE 11 is fully supported except for IE Compatibility Mode – and here's Atlassian's suggested workarounds for that.  

           

          If there is still a compatibility issue with IE 11 other than IE Compatiblity Mode, please reply back with how to reproduce the problem.

          Thanks,

          /Phil

          15 Jul 2015
Powered by Confluence and Scroll Viewport