New code integration features for issues

The new Development panel, which is shown on every issue, helps you to evaluate the development status of an issue at a glance. If you need to investigate further, click any item to display more details, or drill down into the development tool.

Connect to one of these compatible applications to enable the following:

• Bitbucket or Stash: view and create branches, view commits, view and create pull requests
• FishEye/Crucible (Git/Subversion/Perforce/CVS): view branches, view commits, view and create reviews
• Bamboo: view the status of builds and deployments
• GitHub/GitHub Enterprise: view branches, view commits, view and create pull requests

Learn more: Integrating with a development tool and Using the Development panel

Enhanced workflow designer

The workflow designer is faster and easier to use in this release. We've added a range of new features and made the user interface cleaner and less cluttered. You can now click to create transitions, reuse existing transitions, zoom (with the 'alt' key or the +/- controls), drag and drop to retarget the destination of a transition, and more!

In fact, the workflow designer can do everything that we supported in the old 'classic' workflow designer, so we've given the 'classic' designer a well earned retirement and removed it from JIRA.

Learn more...

Simple issue type configuration

We've simplified issue type configuration in this release. Don't hunt around in JIRA administration to find the workflow or screen for an issue type. The issue types associated with a project are now tabs on the project's administration screen.

This approach makes it easier to understand how your projects are set up. Each tab also provides access to the workflow designer and screen designer (JIRA administrators only), so you can configure an issue type without leaving the project.

Learn more...

New status lozenges

This release introduces new "lozenges" to represent statuses in JIRA. We've switched from the old icon+text representation to make it easier for users to locate and identify statuses. The new status lozenges also conform to the Atlassian Design Guidelines (ADG). This blog post explains the background behind this change.

We no longer support custom images for status icons. However, you will be able to configure statuses to use any one of the slick new status colors (categories) in JIRA. 

Learn more...

Auditing

JIRA now tracks and records a range of configuration changes in an audit log. This can help you diagnose problems in JIRA or can be used for security purposes. Find out when a user was added or removed, when a workflow scheme was modified, and more. Note, auditing is disabled by default — you will need to enable it to start tracking changes in JIRA.

This is the initial release of auditing. We're still working on a number of improvements that you'll see in future JIRA releases.

Learn more...

And more!

Of course, there's more! You can read about the other JIRA 6.2 features below. A noteworthy one is that the creator of an issue is now automatically recorded for every issue. This is particularly useful, if you need to know the creator of an issue for compliance reasons. The creator is distinct from the reporter (which can still be configured to be an optional field). On upgrade to this release, JIRA will set the creator to the appropriate reporter in the change history, for existing issues.

The creator can be seen in the issue history. If the creator is the same as the reporter, the name of the creator will be shown in the Reporter field on the issue.

Click to view the other features and improvements in this release: