02 July 2016
Atlassian is proud to present JIRA Core 7.2 RC01. This public development release is part of our Early Access Program (EAP) leading up to the official JIRA Core 7.2 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.2, read the developer change management guide: Preparing for JIRA 7.2. 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.
We want your feedback!
To provide feedback, create an issue in our issue tracker with the following details:
Suggestion
JIRA 7.2 EAP
We've improved the project experience by adding the project sidebar to more features that you use in the context of your project. For users, when you access a report you're now kept in the context of your sidebar, making navigating back to your project quick and easy.
For project administrators and JIRA administrators, we've changed the name of Project administration to Project settings, and we've also changed the layout and positioning:
These changes will help JIRA administrators and Project administrators work more efficiently and effectively.
We've streamlined how you manage components and versions in JIRA Core, and once you've created your first component or version, JIRA administrators and project administrators can manage components and versions directly from the project sidebar.
We've revamped the onboarding for JIRA administrators, when you first log in and select your language and avatar, you're now presented with the options of creating a project, creating a project with demo data, or importing data from an external system. These options are also available to JIRA administrators after they've logged in for the first time:
Your users will also see a more streamlined onboarding, after selecting their language and avatar they can jump right in by looking for existing projects and issues. JIRA administrators can also create projects with sample data for users to look access, the contents of the sample data has been created to give people an overview of JIRA Core and it's features. Give it a try!
We've added the ability to export a list of issues and their associated details in a CSV file. When you search for issues and view the results in a list view, selecting Export now allows you to select a CSV export of either all fields or the currently displayed fields. This export format gives you more options with manipulating the data, and you can even create your own CSV file to import back into JIRA.
We've added the project sidebar to reports, so that you can always stay in the context of your project when viewing JIRA reports. Previously, you would lose your sidebar and have to navigate back to your project, now you're kept in the context of your project.
User's are used to a what you see is what you get experience (WYSIWYG), and expect to see their formatting applied directly to their content. JIRA uses wiki markdown, and previously you had to preview your descriptions, comments and multi-line text area fields to get an understanding of how your wiki markdown syntax will be saved and presented. Now, JIRA administrators can enable the rich text editor, and allow their users to select whether they prefer to stay in wiki markdown, or prefer to experience a WYSIWYG editor.
To enable the rich text editor, select > System, and select Rich text editor from the left hand menu. Then enable rich text editing.
We now include Portuguese (PT), Korean and Russian as supported languages in JIRA.
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:
Rate this page: