After two early access previews (EAP’s) we’ve been working hard to incorporate your feedback into Fisheye 2.7 and Crucible 2.7available for download today!

Fisheye and Crucible deliver a number of new features including a new way to manage your Git Repositories, commits that perform automatic actions in Jira & Crucible and time-saving improvements to your code review workflows.

What’s New in LOGO_Fisheye_Transparent.png

1. Easy Git Repository Management


Administrators can create and manage Git Repositories directly from Fisheye on their own servers. Fisheye Git repository management gives you the flexibility to

  • Create forks and clones of existing projects
  • Manage permissions easily with push and pull access per repository
  • Visualize the hierarchy of repository forks
  • Explore and visualize changes with the commit graph
fe-git-perms.pngEasily manage permissions for your Git Repository.


Visualize the relationships between different forks.

Learn more about setting up your own Git repositories.

2. Time-saving Smart Commits

Smart commits give repository commiters the option of performing actions on Jira or Crucible by adding simple syntax to a commit message. Save time by not having to context switch between applications and improve the workflow of your development activities.

Jira integration

Update Jira issues automatically via specific keywords in your commit messages – workflow transitions, comments and time tracking.

Transition Jira issues

Transition through your workflow by including a Jira Issue Key and the name of the transition with a “#” before the transition name. All transitions that are available to you in Jira can now be done from your commit.

For example, the following syntax will resolve a Jira issue from the command line.

Hint: If you have a transition such as “start progress” just put “JiraKEY-123 #start” in your message to apply this transition.

Comments and Logging Time

Beyond transitioning issues you can also add comments and log time against an issue.

Lets log time and add a comment to an issue:

Crucible integration

Create reviews for all the changes associated with a commit (‘+review’), start a code review (‘+review @reviewers’) or update an existing review (‘+review <Review_Key>’) without going to the Crucible interface.

Here is an example to create a Crucible code review for all the files in a commit. A review is set to Draft mode unless reviewers are added, or there are default reviewers for a project.

To automatically start a review you use the same syntax but need to include the usernames of the Crucible users who will be involved in the review.

Hint: If you have only one project in Crucible you do not need to include the project key. Also, if you are using Fisheye and Crucible and a repository is mapped to a Crucible project you will not have to include the project key.

3. Configurable Web Hooks

fe-Webhooks.pngConfigure URL’s (Web Hooks) in Fisheye that will receive details of each commit made in your repository. This allows you to get events within Fisheye to trigger your external systems with easy to configure Web Hooks.

Trigger a build in your build system, post information to your issues tracker and much more by configuring it from the Fisheye UI.

These are just a few of the many new features in Fisheye 2.7. Other highlights include:

  • Branch HEAD – easily identify which version of a file is a head on a branch
  • Java 7, Groovy and Velocity syntax highlighting
  • Bundled Atlassian Support Plugin to help diagnose and fix problems quickly

Check out the full release notes to learn about all the new features and improvements.

What’s New in LOGO_Crucible_Transparent.png

1. Review Reminders

Sometimes developers forget about code reviews that need their attention. Now you can automatically or manually notify reviewerswho have not completed your code reviews. Set up reminders for reviews with due dates or send manual “nudges” to reviewers who have not completed a review.


2. Stronger Jira Integration

Often times a Crucible code review workflow has a close relationship to the Jira issue workflow. When a users closes (summarizes) a Crucible code review they often jump to a linked Jira issue and transition the issue to a closed or resolved state. With the latest feature integration between Jira and Crucible you can now transition a issue linked to a review from Crucible when closing a Crucible review. No more jumping back and forth between Jira and Crucible to move your workflow forward!


And there is more.

  • Improved OAuth experience with Jira
  • Bundled Atlassian Support plugin get you answers to issues quickly

Check out the full release notes for more details on all of the new features and improvements.

Ready for more

There is more to come! In the coming weeks we will take a deep dive into Git Repository Management, Smart Commits and Web Hooks. Subscribe to the Dev Tools and Developer blogs to keep up to date with the upcoming Fisheye and Crucible blogs.


Download Fisheye 2.7 and Crucible 2.7 now to get started with a 30-day FREE trial or upgrade your current instance.

fe-27-site.png cruc-27-site.png

Fisheye and Crucible 2.7 – Git Repo Manageme...