JIRA 6.2.2 Release Notes

Still need help?

The Atlassian Community is here for you.

Ask the community

1 April 2014

The Atlassian JIRA team announces the release of JIRA 6.2.2. This point release contains several updates and fixes.

Upgrading to JIRA 6.2.2 is free to all customers with active JIRA software maintenance.

Don't have JIRA 6.2 yet?

Take a look at all the new features in the JIRA 6.2 Release Notes and see what you are missing out on!

Important notes

Grant "Browse Project" permission to "Current Assignee bug — fix reverted

In JIRA 6.1.6, we introduced a fix for JRA-31720. After further investigation, we have decided to revert this fix due to performance issues (e.g. JRA-36699). This means that JIRA will revert to its original behaviour, which is described below:

  • If you grant the "Browse Project" permission to "Current Assignee" in a project permission scheme, the project metadata (e.g. project name, project key, etc) will be visible to all users.

Unfortunately, this long-standing issue does not have a simple fix. Please watch JRA-31720 for further information. There is also a workaround described in this KB article.

Upgrading from a previous version of JIRA

If you are upgrading, please read the JIRA 6.2.2 Upgrade Notes.

Updates and fixes in this release

JIRA 6.2.2 includes the following updates and bug fixes:

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

Last modified on Oct 12, 2015

Was this helpful?

Provide feedback about this article

In this section

Powered by Confluence and Scroll Viewport.