JIRA 6.0.3 Release Notes
25 June 2013The Atlassian JIRA team announces the release of JIRA 6.0.3. This point release contains several updates and fixes.
Upgrading to JIRA 6.0.3 is free to all customers with active JIRA software maintenance.
Don't have JIRA 6.0 yet?
Take a look at all the new features in the JIRA 6.0 Release Notes and see what you are missing out on!
New default workflow behaviour
In order to be able to start progress on an issue, a user must have the 'Assignable User' permission. When a user starts progress on an unassigned issue, the issue gets automatically assigned to that user. Similarly, any user with this permission can stop progress on an issue, although in this case the issue does not get reassigned to the user doing so.
This is different from the classic default JIRA workflow in the following ways:
- Previously, when you started progress on an issue, it did not change the assignee to the current user. Whoever the assignee was at that time would remain as the issue's assignee.
- In the classic default JIRA system workflow, only the issue assignee was able to execute the 'Start Progress' and 'Stop Progress' transitions. Now, as long as you have , you can execute this step.
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
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.
- We have improved the performance of the JIRA issue collector (see - JRA-31971Getting issue details... STATUS ). Please be aware, if you edit an issue collector (e.g. change the trigger), there may be a delay of up to an hour until users see the updated issue collector in the target system, due to browser caching. Alternatively, the user can refresh the page in their browser to see the updated issue collector immediately.
- The date/time picker for JIRA now works correctly on all browsers (see - JRA-26265Getting issue details... STATUS ).
- There are a few minor security (XSS/XSRF) fixes in this release. Please see the list of fixes below for details.
Upgrading from a previous version of JIRA
If you are upgrading, please read the JIRA 6.0.3 Upgrade Notes.
Updates and fixes in this release
JIRA 6.0.3 includes the following updates and bug fixes: