JIRA 6.2 EAP 6 (m06) Release Notes

6 January 2014

Atlassian is proud to present JIRA 6.2 EAP 6 (m06). This public development release is part of our Early Access Program (EAP) leading up to the official JIRA 6.2 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 feedback on this release here.

If you are a JIRA developer, please see Preparing for JIRA 6.2 as well as our Java API policy for JIRA.

JIRA 6.2 Upgrade Notes


(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.

We want your feedback!

In this release:

 

Key Features

Auditing

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.

We would love to hear your feedback on this feature. Click the  button on the audit log to let us know which events you'd like to see supported in future.

Learn more...

 

More improvements to the workflow designer

The following features have been added to the workflow designer in this release:

  • You can now scroll over the workflow editor with your mouse. Zooming in only occurs when you press the keyboard shortcut for zooming while scrolling.
  • You can easily create transitions with the transition tool.
  • The zoom in and zoom out capabilities have been improved.

Creator of an issue is now recorded

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.

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...

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