JIRA Core 7.1 EAP 01 (m01) Release Notes

14 January 2016 

Atlassian is proud to present JIRA Core 7.1 EAP 01 (m01). This public development release is part of our Early Access Program (EAP) leading up to the official JIRA Core 7.1 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.1, read the developer change management guide: Preparing for JIRA 7.1. If you are new to JIRA, you should also read our Java API Policy for JIRA and the Atlassian REST API policy.

Upgrade notes (including known issues)

(minus)  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:

  • Issue Type: Suggestion
  • Component: JIRA 7.1 EAP


Project issue view

The new "project issue view" for JIRA Core gives you an expanded view of any issue from within a project. Just click the  icon or an issue link in an issue...

And the target issue will be displayed like this...

This new view works exactly like the regular issue view (e.g. keyboard shortcuts, pagination, inline editing, etc) but you'll get much more space without losing the project sidebar.

Granting project permissions

We've updated the way that you edit your project permission scheme. Granting permissions in now done in a dialog — click the Edit link to display the 'Grant permission' dialog, and select the permissions you want to grant, and to whom. Removing someone from a permission is a similar process — find the permission, click Remove and choose what group, role, or user you want to remove.

Viewing your versions

The dropdown for selecting quick filters on the Versions (JIRA Core) page has been removed and persistent 'sticky' labels added in its place. This allows you to quickly filter your versions by Released or Unreleased. The search bar has also been improved.

Access to additional advanced settings in JIRA Cloud

We've listened to your requests, and we've implemented JRA-26866 - Administrators in JIRA Cloud should be able to access General configuration > Advanced configuration RESOLVED . This allows JIRA administrators to edit some of the advanced settings in their JIRA Cloud instance, that were previously restricted to Atlassian Support. Giving JIRA administrators this increased flexibility to manage their instance has been a long requested feature, and we're happy to finally make it a reality.

Comment webhooks

You can now register comment-related events for a webhook in JIRA Core. This lets JIRA Core notify your add-ons or web applications whenever a comment is created, updated, or deleted. Just choose the desired events when creating or updating your webhook. Read the webhooks documentation for details. 

Atlassian Connect add-ons: Checking for JIRA applications

If you are developing an Atlassian Connect add-on, you can now set the can_use_application condition to detect whether a particular JIRA application is licensed and active for the current user. This For example, the following condition would check whether JIRA Software is installed and enabled, and whether the current user can use it according to the application license:

    "condition": "can_use_application",
    "params": {
        "applicationKey": "jira-software"

Entity properties on issue creation

Entity properties are used to add key/value stores to JIRA entities, like issues and projects. Previously, it was only possible to add entity properties to an issue entity after the issue has already been created. In this release, you can now add these properties when creating an issue (REST API only), e.g.

    "fields": {
          "key": "TEST"
       "summary": "Example issue",
       "description": "This is an example issue",
       "issuetype": {
          "name": "Bug"
	"properties": [
		"propertykey" : {}, // valid JSON object here
		"secondPropertykey" : {} // another valid JSON object here

For more information on entity properties in JIRA, see JIRA Entity Properties overview.


Upgrade notes (including known issues)

There are currently no known issues with this milestone.

if you are upgrading from JIRA 6.3.x or earlier, read Skipping Major Versions When Upgrading JIRA. Remember that EAPs are not supported and should not be used in production environments.

Was this page helpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport