JIRA 6.2 Release Notes
Unify issues and source like never before
This release also includes an improved workflow designer, simpler issue type configuration, new status lozenges, auditing, and more!
25 February 2014
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
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.
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 theand screen designer (JIRA administrators only), so you can configure an issue type without leaving the project.
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.
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.
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:
Back up and recover indexes — Configure JIRA to take snapshots of indexes. Recover an index from a snapshot instead of rebuilding the index, if there is a failure. Learn more...
Re-index individual projects — Re-index a single project, rather than re-indexing your entire JIRA instance. Learn more...
New 'creator' JQL field — Find issues by their creator by using the new 'creator' JQL field. Learn more...
New 'attachments' JQL field — Find issues that have attachments or issues that do not have attachments with the new 'attachments' JQL field. Just add the clause "attachments IS EMPTY" or "attachments IS NOT EMPTY" to your advanced search query. Learn more...
Filtering for User Picker custom field — You can now limit the users that can be selected in a user picker custom field, to specified groups and/or project roles. Just configure your user picker custom field and choose the new Edit User Filtering link. Learn more...
Inline editing can now be disabled — Inline editing, i.e. clicking to edit a field, can now be disabled for your JIRA site in the General Configuration options. It is still enabled by default.
- Internet Explorer 11 is now supported
The JIRA 6.2 team
Jeroen De Raedt
Andre Quadros Petry
Tiago Kolling Comasseto
Kuala Lumpur support
Abdoulaye Kindy Diallo
Amanda Wei Sai Nan Wei
Azwandi Mohd Aris
Chung Park Chan
Joe Wai Tye
John Chin Kim Loong
Steven Trung Tran
Voon Kiat Gan
Yew Teck En
Zulfadli Noor Sazali
San Francisco support
Chris Le Petit
Product marketing management
Bryan J. Rollins
Was this helpful?
Thanks for your feedback!