JIRA Core 7.6 EAP release notes

3 October 2017

Atlassian is proud to present JIRA Core 7.6 EAP. This public development release is part of our Early Access Program (EAP) leading up to the official JIRA Core 7.6 release. We are making these EAP and Release Candidate 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.6, read the developer change management guide: Preparing for JIRA 7.6. 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.

Priorities per project

We're currently working on a way to assign separate, unique priorities to each of your projects, as opposed to having a common set of priorities, like it is now in JIRA.

JIRA 7.6 will introduce a concept of priority schemes that let JIRA admins add new priorities and choose projects they're assigned to. Because of that, the global list of priorities will be deprecated, and replaced with a default priority scheme that contains all priorities and is assigned to all projects. We don't expect any problems for users in JIRA as the default priority scheme is an equivalent of the current global list, and works in the same way. We're still in the early stages of developing this feature, and this EAP milestone doesn't bring any changes to the UI.

What it brings is necessary changes to API. To manage priority schemes, we added new APIs, deleted some, and improved some more, so they can handle the new schemes. If you're an add-on developer and your add-on is using the priorities' API in any way, take a look at the complete list of changes you should be aware of: Preparing for JIRA 7.6.