Rate this page:
30 May 2016
Atlassian is proud to present JIRA Software 7.2 EAP 01 (m01). This public development release is part of our Early Access Program (EAP) leading up to the official JIRA 7.2 release. We are making these EAP milestones publicly available so that developers can start assessing the impact of the changes that we are making.
For the full list of changes for JIRA 7.2, read the developer change management guide: Preparing for JIRA 7.2. If you are new to JIRA, you should also read our Java API Policy for JIRA and the Atlassian REST API policy.
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!
To provide feedback, create an issue in our issue tracker with the following details:
When you view a JIRA Software board and select an issue, the details of the issue display in the issue detail view to the right of your screen. Previously, you were limited to the fields you could edit in the issue detail view, now we've added the ability to edit the issue from this view. This keeps you in the context of your board, which lets you work that little bit more efficiently and effectively. This also allows us to close a long running feature request with over 340 votes!
When cloning an issue that has already been added to sprint, you can now decide whether you'd like to copy the sprint value (the sprint it's assigned to) when you create the clone, effectively adding the cloned issue to the sprint. Simply select the relevant check box when cloning the issue.
We've made a number of improvements which allow you to use JIRA Software that little bit more efficiently. You can now:
All of the changes in the JIRA Core 7.2 EAP are also in the JIRA Software 7.2 EAP unless otherwise stated below. Read the JIRA Core 7.2 EAP 01 (m01) Release Notes for details.
We don't support upgrading to or from EAP releases, and you should never use an EAP release in production. If you do intend to upgrade an instance to an EAP release, you should review all applicable upgrades notes for the production releases, and upgrade in the specified order:
Rate this page: