Crucible Latest (3.2) : Crucible 3.2 release notes

27 November 2013

Today we're excited to release Crucible 3.2, which brings a range of usability and platform improvements.

If you are upgrading from an earlier version of Crucible, please read the Crucible upgrade guide. Please also read the End of Support Announcements for Crucible.

The Crucible 3.2 changelog is at the bottom of this page.

Quick Search filters

We've added filters to QuickSearch, to make finding the content you want even... quicker!

Now, in Crucible 3.2, you can also filter by the last modified date and by author. 

Of course, for a while now, you've been able to filter search results by reviews and review comments, and restrict the search scope for reviews to a particular project. And when used with Atlassian FishEye, you can filter for different source types such as files and directories, commit messages, diffs, file content, and committers.

Read more about searching in Crucible...

Internally managed Git repositories are no longer supported

As previously announced, internally managed Git repositories are no longer supported by FishEye 3.2.

Please read the migration guide for information about options and procedures for migrating your internally managed Git repositories.

Crucible communication with JIRA versions older than 5.0 is no longer supported

As previously announced, communiation with JIRA versions older than 5.0 is no longer supported by Crucible 3.2. Please note that communication from JIRA to Crucible will continue to work as it currently does.

Small improvements

Platform upgrades

See Supported platforms.

Improved protection against XSRF attacks

We've added a security token to protect Crucible from XSRF attacks and to allow plugin developers to add protection to their plugins. See the Crucible upgrade guide for details of changes required by LightSCM plugins.

User data moved to the SQL database

To prevent any chance of loss, the user data store has relocated. See the Crucible Upgrade guide for details.