JIRA 6.2 Upgrade Notes

Please follow the instructions in the general Upgrading JIRA guide, as well as the JIRA 6.2-specific instructions below. The general guide contains important tasks that are essential for getting your upgraded JIRA installation to work correctly and, if necessary, migrating existing configurations.

This page also describes known issues as well as changes you should be aware of before deciding whether or not to upgrade to JIRA 6.2.

On this page:

Information for JIRA developers

See Preparing for 6.2 for important information that could affect your add-ons or scripts. Also, see our Java API policy for JIRA.

Upgrading to JIRA 6.2 from JIRA 6.1.x

Advance notice: End of support for Internet Explorer 8 (post-JIRA 6.2)

JIRA 6.2 will be the last major release that supports Internet Explorer 8 (IE8). For more information, please see this page.

Images are now correctly shown in email notifications

This release fixes a highly-voted bug where images would only be shown in email notifications, if the user is accessing their email in the same session that has been used to log into JIRA. For details, see JRA-25705 - Images are not shown in email notifications Resolved .

(warning) This feature means that mail is now sent in a multipart content type. Please ensure the SMTP JIRA uses supports this.

Labels and Popular Issues tabs removed from Project Overview

The Labels and Popular Issues tabs are not used very much, so we have removed them to simplify the Project Overview page.

Rename user and JIRA as a Crowd server

In JIRA 6.0 and 6.1, the rename user function was disabled if you had JIRA configured as a Crowd server. In this release, the rename function is enabled by default, even if you have JIRA set up as a Crowd server.

If you want to disable rename user when JIRA is configured as a Crowd server, change jira.option.user.crowd.allow.rename to false in the advanced settings. For example, some client applications (depending on JIRA's Crowd server implementation) misinterpret renamed users as having been deleted and created again, so you may want to disable rename user.

For developers: Source distribution — Internal Atlassian dependencies are now Maven-based archives

The internal Atlassian dependencies for JIRA's source distribution are now Maven-based archives, rather than exports of the source repository for each dependency. There will be a Maven-based archive for each dependency, named <dependencyname-version>-sources.jar. For more information, see Preparing for JIRA 6.2.

Upgrading to JIRA 6.2 from JIRA 6.0.8 or earlier

In addition to the points listed above, please read the Important Version-Specific Upgrade Notes for every version of JIRA you are skipping.

Note, you cannot upgrade from JIRA 4.3.x or earlier, directly to JIRA 6.2. You must upgrade to an interim version first. See Skipping Major Versions When Upgrading JIRA.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport