JIRA 6.2 came out on February 25th 2014 and everyone wants to know what are the new features. Here are some of the key features that are available.
This release introduces new "lozenges" to represent statuses in JIRA. JIRA has 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. This blog post explains the background behind this change.
JIRA 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 activities in an audit log. Find out when a user was added or removed, or even when a workflow scheme was modified. The audit log doesn't record every single event in JIRA, but it does capture configuration changes that can impact users and projects. This can help you diagnose problems in JIRA or can be used for security purposes.
Note, auditing is disabled by default. You will need to enable it to start tracking changes in JIRA.
This feature pretty much replaces the JIRA Auditor paid add-on.
Issue types associated with the project are now listed on the main project administration page. The issue type tab has also been redesigned, allowing you to access the or screen designer for the issue type with a single click.
Workflow veterans knew about Common Transitions being limited to the Legacy Workflow Designer. With JIRA 6.2, common transitions are also available in the "new" Workflow Designer. Just add a transition and choose the Reuse a transition tab.
You will only be able to reuse transitions that have the same destination status as the new transition you are adding — the values inTransition to reuse field will change depending on the value of the To Status field.
Other features that have been added to the workflow designer include:
One of the JIRA best practice we teach our clients is to never mess around with the Reporter field, because your users should be able to trust that it corresponds to the actual person who created the issue.
With JIRA 6.2, 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. You can also search for issues by creator.
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.
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.
Internet Explorer 11 is now supported.
Source: JIRA 6.2 RC 1 Release Notes