15 September 2015
Atlassian is proud to present JIRA 7.0 RC3 (note, there was no 7.0 RC1 or RC2 release). 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.
A release candidate (RC) is a more mature build of a development release, and generally does not introduce new changes. The intent of an RC is to provide bug fixes and tweaks to features introduced in earlier EAP releases.
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)
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
JIRA 7.0 introduces a fundamental change to JIRA: applications. Applications are now fundamental to JIRA's licensing, user management, and user interface.
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.
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:
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:
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.
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).
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.
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.
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:
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.
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.
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 |
|
Notes |
|
Updated project templates:
Agile Software Development - Scrum |
|
Agile Software Development - Kanban |
|
Software Development |
|
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.
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.
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 has been upgraded to version 2.8.3, which fixes this bug: JRA-43968.
Atlassian Soy Template Renderer has been upgrade from 4.0.4 (in m03) to 4.1.2 in this upgrade. This new version includes performance improvements. See JIRA 7.0 - Platform changes for details.
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.
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.
The following JIRA EAP downloads include JIRA Agile.
Please take note of the following information when installing or upgrading to this EAP release:
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.
Rate this page: