JIRA 6.1 EAP 3 (m03) Release Notes

15 July 2013 

Atlassian is proud to present JIRA 6.1 EAP 3 (m03). This public development release is part of our Early Access Program (EAP) leading up to the official JIRA 6.1 release. We are making these EAP milestones publicly available so that developers can start assessing the impact of the changes that we are making.

Important Information for JIRA Developers

If you are a JIRA developer, please see Preparing for JIRA 6.1 as well as our Java API policy for JIRAJIRA 6.1 EAP 3 contains breaking changes that could stop your add-ons from working.

We are announcing potentially breaking changes as far in advance as possible; check this Summary of Changes for details.

Please provide us with your feedback here.


(minus) Read before you install/upgrade: Atlassian does not support upgrades either 'from' or '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.

Key Features 

Custom fields have changed

Custom fields are now split into Standard and Advanced categories, and each standard type presents you with an image so that you can see in advance what you are creating. This makes sure that you get the custom field you want, much faster.

(info) To configure search templates or add contexts to custom fields, use the 'Configure' option on each custom field. This is no longer part of the custom field creation process.

New look for email notifications

Email notifications are improved in JIRA. For details, check here.

New default workflow behaviour

We've simplified JIRA's out of the box experience, with new, better defaults:

  • By default, JIRA allows unassigned issues
  • The default workflow allows transitions when you're not the assignee

Previously, by default JIRA required an assignee anytime you created an issue, and the default workflow required you to be the assignee when you transition an issue.  You can always change back to the old behavior, or just import the Classic Default JIRA Workflow from Marketplace (described below).

Classic JIRA workflow available from Atlassian Marketplace

The classic default JIRA system workflow prior to this JIRA release is now available on Atlassian Marketplace.

If you import this workflow, you will need to add the 'Clear Resolution' post function back to the following three transitions:

  • Start Progress
  • Stop Progress
  • Reopen Issue

To add a new post function, see this procedure.

All newly created issues are now unassigned by default

The default for 'Allow Unassigned Issues' is set to ON for new instances. The 'Default Assignee' is set to 'Unassigned' when you create a new project, see Defining a Project for details.

Existing instances keep the current default ('Allow Unassigned Issues' is set to OFF).

JIRA Redmine Importer now available

The JIRA Redmine Importer plugin allows you to import data from the Redmine Issue Tracker product into your local JIRA site. For more information, see Importing Data from Redmine.


Last modified on Nov 29, 2013

Was this helpful?

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