14 November 2012
With great pleasure, Atlassian presents Crucible 2.9, which introduces the best JIRA integration we have ever built.
- See the change log for Crucible 2.9.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.9 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! |
| Simpler JIRA integration
With Crucible 2.9, linking your instance to JIRA is as simple as Plug & Play. As soon as you create an Application Link between your JIRA server and your Crucible instance, you get all the power of the JIRA / Crucible integration:
You no longer need to create and maintain multiple links between projects in JIRA and projects in Crucible. Maintaining your JIRA / Crucible integration has never been simpler! More...
|
| Better performance of the Reviews tab in JIRAWhen we changed the implementation of the Crucible / JIRA integration we also improved the performance of the Reviews Tab display in JIRA. You will see your reviews in JIRA faster, even without having to create any links between your JIRA project and your Crucible repositories. In other words, with Crucible 2.9 you spend less time administering your instance, while your users get all the relevant content in JIRA in a better way than before.
|
| Faster review creation for large teamsCrucible is a tool that is built to help organizations and distributed teams perform code reviews. When you have large teams you can find that you always have a large number of reviews waiting to be closed. Prior to Crucible 2.9, this could slow down the review creation process because Crucible looked for other reviews where changesets might have been included. With Crucible 2.9 we have removed the Suggested Reviews step during review creation. Not only does this accelerate the process, but it also ensures that performance of the whole Crucible instance is not impacted by a single process. The chart below shows the performance improvement we have seen from this modification.
|
| Other announcements
|
hidden text to maintain the column width | The Crucible 2.9 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 |
Attachments:






