FishEye 3.2 release notes
27 November 2013
Today we're excited to release FishEye 3.2, which brings a range of usability and platform improvements.
The FishEye 3.2 changelog is at the bottom of this page.
High design values with the ADG
We've been applying the Atlassian Design Guidelines to make using FishEye a better experience – the layout and behavior have been improved, and if you use other Atlassian products then FishEye will feel very familiar from the moment you log in. In particular, for FishEye 3.2, the navigation menu and the headers for the Changeset and Source pages have been improved for better clarity. For example, the Changeset page now has a much cleaner layout:
SCM checkout URLs
Sometimes when you're looking at source in FishEye you want to be able to access the code locally. We've made that much easier now by providing checkout or clone URLs at the top of the page for a repository.
For example, if you're using SVN, click Checkout, and copy the URL:
If you're using Git, click Clone and copy the URL:
If you're already using Atlassian SourceTree, simply choose Clone in SourceTree, to have SourceTree manage the clone operation for you.
FishEye admins can control the display of the URL for the whole FishEye instance and for particular repositories. See Checkout URLs for details.
Quick Search filters
We've added filters to Quick Search, to make finding the content you want even quicker!
Now, in FishEye 3.2, you can also filter by the last modified date and by author. Sensibly, FishEye restricts some combinations of filters – for example, you can filter diff results by the last modified date, but not by author.
Of course, for a while now, you've been able to filter search results by different source types such as files and directories, commit messages, diffs, file content, and committers. And when used with Atlassian Crucible, you can filter by reviews and review comments. and restrict the search scope for reviews to a particular project.
Read more about searching in FishEye...
FishEye communication to JIRA versions older than 5.0 is no longer supported
As previously announced , communication from FishEye to JIRA versions older than 5.0 is no longer supported by FishEye 3.2. Please note that communication from JIRA to FishEye will continue to work as it currently does.
- Microsoft SQL Server 2012 is now supported (support for SQL Server 2005 is deprecated).
- Microsoft Internet Explorer 10 is now supported (support for IE 8 is deprecated).
- MySQL 5.0 is deprecated.
- PostgreSQL 8.2 is deprecated.
- The Atlassian AUI plugin has been upgraded to AUI 5.2.
- jQuery has been upgraded to 1.8.3.
- backbonejs has been upgraded to 1.0.
See Supported platforms.
User data moved to the SQL database
To prevent any chance of loss, the user data store has relocated. Read the FishEye Upgrade guide for details.
Improved protection against XSRF attacks
We've added a security token to protect FishEye from XSRF attacks. See the Crucible upgrade guide for details of changes required by LightSCM plugins.
This section will contain information about the FishEye 3.2 minor releases as they become available. These releases will be free to all customers with active FishEye software maintenance.
If you are upgrading from an earlier version of FishEye, please read the FishEye upgrade guide.
The issues listed below are just the highlights of all those that have been resolved for the FishEye 3.2.x releases.
|FE-5208||Administrator password reset|
|FE-4972||Git branch heads with non-ascii characters in commit message not parsed properly in some cases|
FishEye 3.2.5 is a security maintenance release. See FishEye and Crucible Security Advisory 2014-05-21.
|FE-4984||On Windows, Fisheye attempts to make ssh keys private but appears to be unsucessful|
|FE-4974||Showing the UPM admin log can't be shown, if it contains entries made by the admin password user|
Was this helpful?
Thanks for your feedback!