JIRA 7.0 EAP 02 (m03) Release Notes

31 August 2015

Atlassian is proud to present JIRA 7.0 EAP 02 (m03). This public development release is part of our Early Access Program (EAP) leading up to the official JIRA 7.0 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 7.0 as well as our Java API Policy for JIRA.

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 EAP

Changes

Applications

JIRA 7.0 introduces a fundamental change to JIRA: applications. Applications are now fundamental to JIRA's licensing, user management, and user interface. 

  • Licensing — JIRA 7.0 eliminates the single JIRA license in favor of a base platform where multiple applications can be licensed individually. You can install one or more applications in JIRA via the Manage applications page. The base JIRA application, JIRA Core, provides basic project tracking capabilities for business teams. All JIRA applications include access to JIRA Core, or you can license JIRA Core only for users that need basic access to JIRA.
  • User management — Users consume a seat in a JIRA application license when they are granted access to a JIRA application. In JIRA Server, the new Application access page allows administrators to grant access to licensed applications to specific groups. 
  • User interface — In JIRA 7.0, we will be solidifying the concept of project types in JIRA, as well as expanding the capabilities of project types to provide application-specific features available in that project. Installing and licensing an application in JIRA allows user to create projects of that application's project type. For example, if there were an application called "JIRA Space Program," administrators could create new projects with the "Space Program" project type. Users with access to JIRA Space Program will have access to Space Program-specific features in Space Program projects. 

We recommend that you read the Preparing for JIRA 7.0 guide for details on how these changes will affect you.

These changes are enabled by default in this EAP release. More information will be provided about licensing and projects in JIRA 7.0 as we get closer to the public release date.

JIRA Agile REST API

We're pleased to announce that JIRA Agile now has a public REST API. The new officially supported REST API includes a number of improvements over the old private JIRA Agile REST APIs:

  • New resources — We've added a number of new resources to help you interact with JIRA Agile, like the epic and sprint resources.
  • Online documentation — You don't need to mess around looking at private internal API calls anymore. The documentation is available online and will be updated with each release.
  • New documentation theme — The documentation is now easier to parse with expandable sections for resources and better styling.

Check out the documentation for the latest version here: https://docs.atlassian.com/greenhopper/REST/cloud/ 

If you are currently using the private JIRA Agile REST API, see the instructions below:

  If you have a Connect add-on...

Be aware that the resources that are marked as private in  JIRA Agile REST Scopes  have been deprecated. These private resources will no longer be whitelisted on the 1st November 2015. You must migrate to the new public REST API before this date.

Note, there is feature parity between the whitelisted private resources and the new public REST resources.

  If you have a P2 add-on...

Be aware that the private JIRA Agile REST API will remain experimental and may break at any time. You can continue to use the private API, but we recommend that you migrate to the new public REST API.

Note, feature parity does not exist between the private and public REST APIs, and we cannot promise that there will be feature parity in future.

If you have problems using the new JIRA Agile REST API, create an issue in the ACJIRA project on ecosystem.atlassian.net (not the issue tracker shown at the top of this page).

(info) You will need to use the JIRA EAP that includes JIRA Agile to try the new JIRA Agile REST API. See JIRA + JIRA Agile EAP downloads below.

Project types

Every project in JIRA now has a project type. You'll see this in a number of places in this milestone, e.g. when viewing projects or creating projects.

This change means that you must now provide a project type key when creating a project. This applies to both the Java API and REST API for JIRA. For more information, see Preparing for JIRA 7.0 - API changes.

Shared configurations for projects

When you create a project, you can now choose to share the configuration of an existing project with the new project.

The shared configuration consists of the following:

  • Issue Type scheme
  • Issue Type Screen scheme
  • Field Configuration scheme
  • Workflow scheme
  • Permission scheme
  • Notification scheme
  • Issue Security scheme

Project sidebar

The project sidebar that we previewed in JIRA 6.4 is here to stay. We built this new navigation experience to make it easier for you to find what you need in your projects. It's even better, if you are using JIRA Agile: your backlog, sprints, and reports are now just a click away. If you've used the sidebar with JIRA Agile before, you'll notice that boards that include multiple projects now have a project sidebar as well, albeit a simpler version.

Dashboard items

We're making your dashboards faster with dashboard items in this release. Dashboard items are similar to gadgets, but they use more modern technologies and load faster. They are also simpler to develop, if you want to build your own (read the developer guide). We haven't replaced all of the gadgets with dashboard items yet, but this release includes a few, like the pie chart gadget and the administration gadget. 

Changes to project templates

We've made a few changes to the project templates that are used when creating a project. Some templates have been updated with new names and icons. We've also introduced a default issue type, which is used when creating issues, until you select a different one. Check out the changes below:

New project template: "Basic software development"

Workflow
Issue types
  • Bug, Task, Sub-task, Improvement, New Feature, Epic
  • Default issue type = Bug
Notes
  • JIRA Agile is required for this project type.

Updated project templates:

Agile Software Development - Scrum
  • Renamed to "Scrum software development"
  • Default issue type: "Story"
Agile Software Development - Kanban
  • Renamed to "Kanban software development"
  • Default issue type: "Story"
Software Development
  • This project template has been removed

(info) You will need to use the JIRA EAP that includes JIRA Agile to see these three project templates. See JIRA + JIRA Agile EAP downloads below.

Attaching images and files

We've improved the way you can attach an image or file to an issue by allowing you to now drag and drop an image or file to any part of an issue screen. You can also use your regular paste options (using your keyboard or right-clicking) to paste a file or image from your clipboard to the issue. Due to this, we've removed the Attach screenshot menu item, and the Attach file menu item now opens a File browser dialog to allow you to browse to your file or image.

If you're using JIRA Service Desk, agents will also be able to add attachments directly to issues by dragging and dropping, or by pasting, and this will open an additional Add attachments dialog that gives you the ability to add a comment to the issue that relates to the image.

Inline issue create

Some time ago, we released a feature to JIRA Agile known as inline issue create, which gave users the ability to create issues on the fly without the need to click the Create button. In this release, we've added the ability to create issues inline to all projects. Simply click the Create link at the bottom of your issue link, add a summary and press enter to create your issue for that project.

Crowd upgrade

Crowd has been upgraded to version 2.8.3, which fixes this bug: JRA-43968.

New guide: Extending the JIRA Import plugin

This guide helps you extend the JIRA importer plugin to include data from your plugins during project imports. Read the guide here:  Guide - Extending the JIRA Import plugin.

New tutorial: Omit web-resources when your plugin is unlicensed

If your plugin is not licensed in a JIRA instance, you can ensure that web-resources are not loaded to the front end. Omitting these files will improve the performance of the pages that your plugin affects, when the license is missing. Read the tutorial here: Omit web-resources when your plugin is unlicensed tutorial.

JIRA + JIRA Agile EAP downloads

The following JIRA EAP downloads include JIRA Agile:

Upgrade notes (including known issues)

Please take note of the following information when installing or upgrading to this EAP release:

  • Known issue with 7.0 EAP 01 (m01) — The 7.0 EAP 01 (m01) EAP milestone includes an incorrect ehcache.xml configuration file, which prevents JIRA from starting. If you have been using this milestone, we recommend that you use the latest milestone instead.
  • REST API browser does not work with JIRA 7.0 — We recommend browsing our online REST API documentation instead: JIRA APIs.
     

In addition to the points above, 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