JIRA 6.3 EAP 6 (m06-1) Release Notes

06 June 2014

Atlassian is proud to present JIRA 6.3 EAP 6 (m06-1). This public development release is part of our Early Access Program (EAP) leading up to the official JIRA 6.3 release. We are making these EAP milestones publicly available so that developers can start assessing the impact of the changes that we are making.

If you are a JIRA developer, please see Preparing for JIRA 6.3 as well as our Java API policy for JIRA.

JIRA 6.3 EAP 6 (m06-1) Upgrade Notes

(minus) Read before you install/upgrade: Atlassian does not support upgrades both 'from' and 'to' EAP releases. EAP releases should not be used in production environments as they are not officially supported. For all production use and testing of JIRA, please use the latest official release instead.

We want your feedback!

In this release:

Key Features

Small changes to JIRA admin screens

We've made some minor changes to the location of some of the JIRA administration features. The functionality of the features hasn't changed, but we believe their new location will make them more intuitive to find. The following features have been moved from the User management tab to new areas in the administration pages:

Feature Now located in
Roles administration console System tab in a new "Security" section
Global permissions administration console System tab in a new "Security" section
Default user preferences administration console System tab in the "User interface" section
Shared filters administration console System tab in a new "User-created assets" section
Shared dashboards administration console System tab in a new "User-created assets" section

GitHub Importer release

We've now officially released the GitHub importer, and have ensured that it's compatible with JIRA 6.1 onwards. The GitHub importer will allow you to connect to your GitHub account, regardless of whether it's a private or enterprise account, and import any public, private or starred repository configurations into JIRA. You can map the GitHub labels to issue types, resolutions or keep them as JIRA labels. The import process will provide you with a detailed log of your import, so that you can troubleshoot any issues, and also supports importing attachments.

New Audit Log features

We first introduced the audit log in JIRA late last year. In this upgrade, we've added some new features to the audit log:

  • When a role is removed (deleted) from JIRA, previously the audit log would log an event for every project that it was removed from. Now, the audit log will only log the event that the role has been removed from JIRA.
  • We have given administrators the option to hide logged events from external user directories, such as LDAP and Crowd. These events are still recorded, and are still available for export and through the REST API.

Transition Permission

JIRA now has a new Transition Issues project permission that gives administrators more control over what users can do in JIRA. Users without this permission will not be able to transition issues (change the issue's status) in a project.

The ability to transition issues was previously controlled by the 'Browse Projects' project permission. However, after listening to feedback, we have changed the 'Browse Projects' permission so that it now allows users to browse issues, but not transition them.

The Create button

At Atlassian we're constantly working on creating an optimum user experience, and as such we also work on aligning our various products. We have changed the Create Issue button to simply Create. This brings us in line with Service Desk and Confluence, and also gives you a little more room on the top navigation bar!

Inline Version and Component creation for Project Administrators

Project administrators can now add versions and components from within the Fix Version/s, Affected Version/s and Component/s fields. Previously an administrator needed to add a version or component via the appropriate screen on the project's administration page. Now, you are able to create the version or component by typing it in the field and selecting it from the drop-down list. When you begin typing text that JIRA does not recognise as existing, it will add it to the bottom of the drop-down list and add (New Version) or (New Component).

Creating a new version 6.3.


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