13 April 2017
Atlassian is proud to present JIRA Software 7.4 EAP. This public development release is part of our Early Access Program (EAP) leading up to the official JIRA Software 7.4 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.4, read the developer change management guide: Preparing for JIRA 7.4. If you are new to JIRA, you should also read our Java API Policy for JIRA and the Atlassian REST API policy.
We've added an additional option to the Administer Projects permission. When granted, the Extended project administration option will allow project administrators for the associated projects to:
The Extended project administration option can be granted by selecting > Issues > Permission schemes, and then choosing the relevant permission scheme to edit. Note that it will be granted to all project administrators for the projects that use that particular permission scheme.
We've implemented the ability to create a Kanban backlog that displays on a separate screen to your Kanban board. This frees up your board from the weight of a lengthy To Do list, and allows the developers to concentrate on the issues that need to be worked on. You can turn on the Kanban backlog by accessing your standard Kanban board and selecting > Board settings > Columns. You'll see instructions on how to set up your Kanban backlog.
We've implemented an exporter which exports JIRA issues in an HTML format. When viewing a list of issues, select > HTML (All fields) or > HTML (Current fields). A JIRA administrator can disable the HTML export option by setting the property to 'false' at > System and clicking Advanced Settings.
We've implemented a system add-on which provides targeted notifications within your JIRA application, predominantly to JIRA administrators. These notifications will alert you when new JIRA versions are available, and of upcoming license renewals.
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: