Archives for the tag: crucible

We've embedded Crowd (our single-sign on offering) in FishEye & Crucible 4.0. Next, we improved FishEye's blame by making it on-demand. Blame information is now showing up only when you ask for it. Pages are also loading faster with the content block more focused on the code than before. We're excited about this release and confident you will be too by the time you're done reading this post.

Continue reading »

In this release, the team focused on making the day-to-day interaction with your reviews faster and more enjoyable. The new review activity stream puts the entire review discussion at your fingertips. In one click (or keyboard shortcut), you can access new comments or read up on the entire discussion if you joined the review a bit later. To make your review experience even more smooth, the release also includes a number of performance and responsiveness fixes.

Continue reading »

With FishEye and Crucible 3.8, we've introduced a number of improvements to allow teams to increase their development speed. This release brings a number of performance optimizations in several areas, including the activity stream, review dashboard, and Git indexing. We've also extended the patch parser so different diff formats can be accepted for pre-commit reviews.

Continue reading »

Today we are proud to announce the release of FishEye and Crucible 3.6. In this release we've made creating a review from a branch in your SCM much, much simpler and streamlined. We've also continued improvements to the performance and enhanced the overall experience with FishEye and Crucible by adding faster keyboard navigation with the new "Actions" dialog. Try FishEye and Crucible 3.6 for free Branch Reviews Crucible 3.6 makes creating reviews for branches fast and simple. By selecting the

Continue reading »

In almost every organization, team members collaborate to get work done. Software teams typically transition issues between people for different functions like code development, code review, and testing (even if they are all on the same team). When transitioning an issue from one team member to another it’s important to minimize the amount of ramp up required for the receiver to fully understand the issue. Transferring issues can be extremely expensive as it requires time from not only one,

Continue reading »