Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

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. If a platform is not (or no longer) supported by JIRA 6.3 EAP, it is not listed in this table.

Platform/FunctionalityJIRA end of support
Internet Explorer 8From JIRA 6.3 (announcement)

Why is Atlassian ending support for these platforms?

Icon

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.

On this page (most recent announcements first):

Deprecated web browsers for JIRA (October 2013)

This section announces the end of Atlassian support for Internet Explorer 8. Atlassian will not fix bugs related to Internet Explorer 8 past the support end date, except for security-related issues.

We will stop supporting the web browsers:

  • From JIRA 6.3, due in 2014, JIRA will no longer support Internet Explorer 8.

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 Internet Explorer 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 OnDemand.

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 OnDemand. 

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)

Icon

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 OnDemand). 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.
  • No labels

24 Comments

  1. 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.

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

  2. 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

    1. 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.

      1. 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

        1. 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.

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

          2. 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...

            1. 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

          3. 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!

             

  3. 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.

    1. 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...

  4. 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 ?

  5. 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.

     

    1. have you read the notification above?

       

      Icon

      … 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)

  6. +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.

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

    1. Hi Matt,

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

      Kind Regards,
      Andrew

      1. 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.

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

  8. 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?

    1. Hi,

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

      Kind Regards,
      Andrew

  9. 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?

  10. 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 Open