JIRA 6.2 EAP 4 (m04) Release Notes

9 December 2013

Atlassian is proud to present JIRA 6.2 EAP 4 (m04). 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


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.

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

Last modified on Dec 12, 2013

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.