JIRA 6.1 EAP 5 (m05) Release Notes
12 August 2013
Atlassian is proud to present JIRA 6.1 EAP 5 (m05). 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
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.
Easier column configuration
JIRA lets you change the columns of the table of search results for any search results displayed using the List view (as opposed to the Detail View). Click the icon at top right of the issue table to open the column configuration dialog, shown below.
JIRA password policy
The JIRA password policy feature enables JIRA Administrators to set limits and restrictions on the types of passwords their users can create. Use this feature to create a more secure JIRA system for your company. Read more...
Custom fields types have changed
When creating a custom field, you now can choose between Standard and Advanced types. For Standard types, a preview image is shown for each type, so you can see what you are creating in advance. This ensures that you get the custom field you want, much faster.
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
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.
Removal of JQL function "echo()"
The echo function is a testing function in JIRA. It has been removed from JIRA as it provides no user value. Existing filters that make use of this function will no longer work; please fix these filters, or remove them.