15 January 2013
With great pleasure, Atlassian presents Crucible 2.10, which introduces the best JIRA integration we have ever built.
- See the change log for Crucible 2.10.x minor releases.
- Visit our issue tracker to see the full list of improvements and bug fixes in Crucible and FishEye for this release.
- Upgrading from a previous version of Crucible. Upgrading Crucible should be fairly straight forward. We strongly recommend that you back up Crucible before upgrading. Please refer to the Crucible 2.10 Upgrade Guide for further essential information about your upgrade.
- Known Issues. Please check the important technical advisories on the front page of the Knowledge Base for information about any known issues for this release.
- JIRA 5.0 integration. The features described below are supported by JIRA 5.0, or later, with the latest version of the JIRA FishEye plugin.
Highlights of this release: | Providing feedback:Please log your votes and issues. They help us decide what needs doing, and are much appreciated! |
Inline Issue CreationWith Crucible 2.10 you can now create any type of issue from your reviews. You only need to link your Crucible and JIRA instances to get it working. Once this is done you can create issues in any JIRA project you have access to, as well as create subtasks if an issue is linked to your review. |
Repository Management REST APICrucible 2.10 lets you optimize your instance by using the REST API to trigger indexing when it's necessary. Instead of configuring Crucible to poll each repository every minute, you can add a post-commit or post-receive hook to your repositories which will ping Crucible when new commits need to be indexed. If your repositories are hosted on Bitbucket or Github you will find corresponding Service Hooks in the settings of your repositories which will do the job for you.
|
Repository review creation limitCrucible 2.10 now has a limit to prevent oversized reviews from being created during wrong manipulations. We have set the limit fairly high at 800 file revisions, a number way above the recommended number of files per review. The limit will help to prevent your instance from having performance issues. |
Other announcements
|
hidden text to maintain the column width | The Crucible 2.10 team |
hidden text to maintain the column width | DevelopmentCore teamBrendan Humphreys Team leadNick Pellow Product managementSten Pittet Project managerAnton Mazkovoi | SupportAjay Sridhar OthersProduct marketingGiancarlo Lionetti Quality assuranceGeorge Filippoff Technical writingPaul Watson OperationsJames Fleming |