Create JIRA Issues From Code Reviews
Crucible is taking the integration with JIRA to the next level with Inline Issue Creation. Link your Crucible instance to JIRA and turn any comment into a JIRA issue. Development teams can improve code quality and save time by transforming important Crucible review comments into easily traceable JIRA issues during the code review process.
Developers all over the universe use of FishEye’s smart commits to create, update, and resolve issues and reviews programmatically. Now the same applies to review objectives in Crucible. Use the smart commit syntax to add objectives to reviews as you’re creating them, or to existing reviews – without having to switch over to Crucible.
Keeping Things Fast
In the 2.8 and 2.9 releases, we removed architectural bottlenecks so FishEye and Crucible can keep up with the growing size of our customers' repositories. Not only did we continue core performance improvements in 2.10, we added a new REST endpoint that gives your hard-working servers a little relief.
Instead of polling repositories once a minute, you can now trigger re-indexing only when something in your repo has actually changed. Optimizing FishEye and Crucible with post-commit hooks for indexing slashes server load and makes every operation faster, especially for Enterprise teams: page loads, reviews and reports.
There are loads of things that can get in the way of your team’s productivity – but configuring your development tools shouldn’t be one of them. Administrators are routinely looking for ways to save time, cut down on common requests and get their development teams up and running quickly. The FishEye and Crucible team has delivered a set of new features to make system administrators’ lives a whole lot easier by simplifying the integration between FishEye, Crucible and JIRA.
- Save time: teams with large repositories and projects no longer need to create and maintain multiple links between projects in JIRA and repositories in FishEye, this is now done automatically.
- Cut down on common requests: never get another request to connect a FishEye or Crucible project to a JIRA project. Your JIRA instance now gets data from all projects existing on your FishEye and Crucible server automatically – no mapping required.
Continuing our focus on performance, this release delivers improvements to strip off seconds for several common operations between JIRA, FishEye and Crucible – specifically the Source and Review Tabs. Large instances with multiple repositories, each with many changesets will get relevant information up to 10x faster when viewing the Source and Review tabs in JIRA. Check out the difference from data tested on a load testing instance of FishEye and Crucible with multiple repositories and changesets.
Faster Review Creation for Larger Teams
We realized that developers know instinctively what needs to be reviewed and what doesn’t. So we axed the “Suggested Reviews” step when creating reviews – a step that was taxing both for the review creator and the Crucible instance itself, especially for larger instances. By removing it, we streamlined performance for both human and machine.
Focus on Performance
We started with the concept of improving page load times as the area where we can create the biggest customer benefits around performance. While the improved page load times ripple out across the product, we saw the biggest gains with Activity Streams. Activity Stream page load times have improved by up to 50 times. Check out the difference from data tested on a load testing instance of FishEye and Crucible.
Did we stop at Activity Streams? Nope. The FishEye and Crucible Performance Team made improvements to load times of other key pages, including the Projects list (that one’s for you, Enterprise users!).Learn more about Crucible's focus on performance»
Easily bring members of your team into a code discussion by @mentioning them in a review or changeset comment. Just type “@” + their name as part of your comment and they will receive a notification that they have been mentioned. From there, the conversation can take place in Crucible or changeset comments where it’s available to everyone, instead of being hidden in your email. Pull them into the conversation – your code will benefit from it!Why @mention? Learn more...
Share Reviews with your Team
Software development is not just about coding. It’s a network of developers collaborating on a common project. When collaborating, it is important to get information to members of your team (and outside your team) fast. Every aspect of Crucible is easy to share between team mates because everything is just a URL away. All it takes to share any artifact with your team is switching over to your email or IM applications to share information.
Crucible 2.8 makes the sharing of information super-quick. With the new Share Button you can instantly share reviews with members of your team or users new to Crucible. That means no switching between applications! Click Share, specify the users you’d like to notify by username or email address, provide a quick message for context and Crucible will keep your team up-to-date.
Subversion 1.7 Support
Satisfying a highly voted feature request, we now fully support Subversion 1.7, making FishEye and Crucible more compatible with your Subversion environments.