Integrating FishEye with Atlassian applications

When FishEye is integrated with JIRA you can:

• Use smart commits to transition JIRA issues
• Delegate user and group management to JIRA

When Crucible is integrated with JIRA, you can:

• Transition JIRA issues

When JIRA is integrated with FishEye, you can:

• View an issue's FishEye changesets
• Browse a project's FishEye changesets
• Add the FishEye Charts Gadget to your JIRA dashboard
• Add the FishEye Recent Changesets Gadget to your JIRA dashboard
• View an issue's Crucible reviews
• Browse a project's Crucible reviews
• Add the Crucible Charts Gadget

When FishEye is integrated with Crucible, you can:

In FishEye:

• Use smart commits to create Crucible reviews, add reviews to new reviews and update an existing review.

In Crucible:  

• When using Iterative reviews in Crucible, you will be prompted when a new version of a file is available.
• Files and changesets displayed in activity streams (e.g. the dashboard activity stream) render as links to the relevant files/changesets.
• See your content roots and repositories associated with projects.
• See repository lists and browse repositories using the Files tab.
• View charts or code metrics.

See also What happens if I decide to stop using Fisheye with Crucible.

When FishEye is integrated with Stash:

• You can easily add Stash repositories to FishEye with a single click. Once added, the repository behaves just like a native repository in FishEye, so your team gets all the benefits of FishEye indexing, browsing and searching. Furthermore, the repository becomes available to Crucible, so you can perform in-depth code reviews for changes in the repository.
• A push to a Stash repository that has been added to FishEye automatically triggers FishEye to run an incremental index. You don't have to configure polling for new commits, or set up dedicated FishEye web hooks in your Stash instance.

See:

• Integrating Crowd with Atlassian FishEye
• Integrating Crowd with Atlassian Crucible

When FishEye is integrated with your Bamboo continuous integration server, you can view the code changes that triggered a build. When a build fails due to a compilation error or failed test, you can explore the failed build in FishEye and jump directly into the changeset that broke the build. You can view the history of that changeset to see what the author was trying to fix, take advantage of the the side-by-side diff view to analyze the change and then open the correct files in your IDE.

For more details see Viewing the Code Changes that Triggered a Build.