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-31971 - Issue collector causes performance issues on host JIRA instance Resolved ). 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-26265 - Date Time custom field doesn't calculate current time Resolved ).
- 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:
|JRA-33788||Basic search in Issue Navigator can't find by username to autocomplete in Assginee and Reporter field||Jul 09, 2013||Feb 20, 2017||Unassigned||Amanda Wei [Atlassian]||Closed||Obsolete|
|JRA-33355||After logo upload, "Undo" link doesn't revert the colour scheme||Jun 03, 2013||Feb 20, 2017||Oswaldo Hernandez||Graeme Smith||Resolved||Fixed|
|JRA-33262||Mentions drop-down stalks in detail view||May 27, 2013||Feb 20, 2017||Oswaldo Hernandez||Luis Miranda||Resolved||Fixed|
|JRA-32739||Return to search link disappears after adding screenshot to issue||Apr 23, 2013||Feb 20, 2017||Unassigned||Jason Stubbings||Resolved||Cannot Reproduce|
|JRA-34087||The Issue Collector should cache its state and not reload it from the database on every request||Jul 29, 2013||Jul 30, 2013||Unassigned||Kelvin Yap||Resolved||Duplicate|
|JRA-33993||Radio Button error message is not aligned||Jul 22, 2013||Feb 20, 2017||Unassigned||Pietro Schaff||Resolved||Fixed|
|JRA-33543||The tab ordering within Issue Navigator is incorrect||Jun 18, 2013||Feb 20, 2017||Oswaldo Hernandez||Eric Dalgliesh||Resolved||Fixed|
|JRA-33542||viewing an issue in the issue nav does not update current project||Jun 18, 2013||Feb 20, 2017||Oswaldo Hernandez||Eric Dalgliesh||Resolved||Fixed|
|JRA-33541||Random placement of mentions dropdown||Jun 18, 2013||Feb 20, 2017||Oswaldo Hernandez||Eric Dalgliesh||Resolved||Fixed|
|JRA-33540||JS Error: "Cannot call method 'nextIssue' of undefined" pressing 'j' on an issue||Jun 18, 2013||Feb 20, 2017||Oswaldo Hernandez||Eric Dalgliesh||Resolved||Fixed|
|JRA-33539||Mentions drop down remains visible after pressing ESC to cancel inline edit||Jun 18, 2013||Feb 20, 2017||Oswaldo Hernandez||Sergio Cinos||Resolved||Fixed|
|JRA-33511||Merging multiple versions can lead duplicate key errors from the database||Jun 16, 2013||Feb 20, 2017||Oswaldo Hernandez||Brenden Bain||Resolved||Fixed|
|JRA-33330||Uncategorised Projects list missing in the Edit Project Roles page||May 30, 2013||Feb 20, 2017||Oswaldo Hernandez||Chung Park Chan||Resolved||Fixed|
|JRA-33310||Issue Navigator does not allow searches based on a Custom Field named 'Progress'||May 29, 2013||Feb 20, 2017||Oswaldo Hernandez||Matheus Fernandes||Resolved||Fixed|
|JRA-33105||Automatic look and feel undo doesn't seem to work||May 17, 2013||Feb 20, 2017||Unassigned||Steve Deary||Closed||Duplicate|
|JRA-32904||When sharing an issue in JIRA ondemand-fireball-216-11-gffe2c38, scrolling to the bottom of the share dialog causes it to dissapear, losing content||May 03, 2013||Feb 20, 2017||Oswaldo Hernandez||Matthew Moor [Atlassian]||Resolved||Fixed|
|JRA-31971||Issue collector causes performance issues on host JIRA instance||Mar 05, 2013||Jan 05, 2017||Oswaldo Hernandez||Andreas Knecht||Resolved||Fixed|
|JRA-31130||"Auto-update search results" description in General Configuration is unhelpful||Jan 02, 2013||Feb 20, 2017||Oswaldo Hernandez||Penny Wyatt||Resolved||Fixed|
|JRA-29088||Time zone contradicts on Date Picker field with Google Chrome||Jul 25, 2012||Feb 20, 2017||Unassigned||Shapla Khanam [Atlassian]||Resolved||Duplicate|
|JRA-27515||monospaced formatting does not allow links||Mar 14, 2012||Feb 20, 2017||Unassigned||Hans Ginzel||Resolved||Obsolete|
Was this helpful?
Thanks for your feedback!