JIRA 6.3 EAP 2 (m02) Release Notes

7 April 2014

Atlassian is proud to present JIRA 6.3 EAP 2 (m02). 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 2 (m02) 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.

 

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