JIRA 6.0 EAP 4 (m06) Release Notes

4 February 2013 

Atlassian is proud to present JIRA 6.0 EAP 4 (m6). This public development release is part of our Early Access Program (EAP) leading up to the official JIRA 6.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.

Please provide us with your general feedback here; and please provide us with your design (i.e. new look and feel) feedback here.

Important information for developers

We intend for this release, the EAP 4 (m6) milestone, to be the last release that includes "breaking changes" for JIRA 6.0. "Breaking changes" are changes to the JIRA APIs that require ecosystem developers to change how they build their plugins. These include changes to JIRA's stable (Java) API, changes to core JIRA CSS styles, changes to JavaScript components that build UI, changes to HTML markup patterns.

You should start updating your plugins for JIRA 6.0 now. We are not planning on making any further breaking changes, but if they do occur in future EAP releases, we will ensure that they are highlighted in the release notes. For details on all of the developer changes for 6.0, see Preparing for JIRA 6.0. Please also see our Java API policy for JIRA for technical information on the JIRA Java APIs and our approach to changing them.

(minus) Read 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.

Key Features 

 

A new JIRA look and feel

The JIRA look and feel is being redesigned in JIRA 6.0 according to the new Atlassian Design Guidelines. We want to provide you with an amazing user experience that helps you get your work done as effectively as possible. These changes are being progressively implemented during 6.0 development.

We are not there yet, so some things may not look quite right. However, you'll notice design improvements to a number of screens in JIRA, including the Project Summary page in the Administration Console and the Create/Edit issue screen.

If you are a developer, these changes will affect you; start making changes to your plugins now. The following documents are designed to help you with this transition:

(info) We'd love to hear your feedback on the new JIRA look and feel. Please provide us with your feedback here.


In this release:

 

Issue navigator improvements

Stable search

Now, when you search, your search results remain constant until you choose to refresh them. This provides you with a stable set of search results that you can work from when triaging issues. And, since your search results don't change as you are making changes to the list, you maintain the original list you started with.

(info) We are in the early stages of testing this feature, you can help by providing us with feedback. We'd like to know what works and what doesn't. Does this feature help when you are working with a large number of issues? How could it be better? To provide feedback, click Give Feedback at the top right of your JIRA screen.

A faster view issue experience

In this release, we've streamlined the interaction with the View Issue screen and removed page loads to speed things up. We've also made additional performance improvements that make navigation between issues much faster. This makes going from stable search to viewing an issue and back again much faster. We will continue to improve performance for searching and viewing issues during JIRA 6.0.


 

Workflow improvements

Global workflow schemes

Now you can edit an active workflow scheme on a project: a draft is created, and the migration is handled through the normal migration process. The following functionality is available:

  • Add existing workflows
  • Remove workflows from scheme
  • Reassign issue types between workflows in the scheme
  • Publish draft
  • Discard draft

In addition to this, workflow schemes can be edited even if they are associated with more than one project.

Read more...

Workflow sharing

The new Workflow Sharing feature allows you to share your team's workflow with other teams in your organisation on different JIRA instances, or external parties in other organisations via the Atlassian Marketplace. This feature allows you to easily use workflows that other people have published, or to move a workflow from staging to production in your own organisation.


 

Read more...


 

Get started faster

Faster JIRA setup with the new administration gadget

We're in the process of redesigning JIRA to help new administrators and users of JIRA get started faster. In this milestone, we've overhauled the administration gadget, which is displayed on the default dashboard for JIRA administrators.

The new administration gadget now displays a handy checklist of common tasks. Click on any task and you'll be taken to the relevant administration screen to complete it. The gadget also provides other helpful information for new administrators, such as links to the JIRA administrator documentation and license details.

Read more...


 

New plugin points for the User Profile page

For the ecosystem developers, we have implemented new plugin points for the web panels in the User Profile page. You can override the default 'Details', 'Preferences' and 'Assigned Open Issues per Project' web panels as well as add your own custom web panels.

Read more...


 

Other improvements

Administrators can edit usernames

JIRA Administrators can now edit any username in the JIRA Internal Directory (this is often referred to as the "rename user" feature). This ability is important to have when you connect JIRA to an LDAP directory and the username format is different, so now you can edit the usernames before you connect to your LDAP directory and have them match. The other most common use case is when a staff member wishes to change their surname. Once the username is changed in the internal directory, all parts of the JIRA interface display the updated username.

Auto look and feel

You can now create a new look and feel for your JIRA instance based on your company's logo. When you upload your company logo, you can choose to have JIRA change your colour scheme based upon the colours in your logo (see example below).

If you don't want to accept the change, simply click Undo in the displayed message.

Global autowatch configuration

We've implemented a new JIRA option that allows administrators to disable the autowatch feature (introduced in JIRA 5.0.3) for all users. To configure autowatch for all users, navigate to Administration > User Preferences (in Users section) > Default autowatch.

Users can choose to inherit the global autowatch setting or override it via their user Profile > Preferences > Autowatch setting.

Please note, if you are upgrading from an older version of JIRA, then all users who have not explicitly set their Autowatch setting will have it set to 'Inherit from global settings'.

Maximum project name size and maximum project key size configuration

JIRA administrators will be able to set the maximum size for both the project name and project key in this release. Navigate to Administration > System > General Configuration and update Maximum project name size or Maximum project key size as desired.

The Maximum project name size or Maximum project key size are defaulted to 80 and 10 respectively. This will not affect the names or keys for your existing projects.

Reports have moved

We have moved reports from the dropdown menu on the Browse Project > Summary tab to a panel on the same tab. This makes the reports more accessible and presents a cleaner user interface.


Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport