すべてのバージョン
Fisheye 4.2 ドキュメントFisheye 4.1 ドキュメント
Fisheye 4.0 ドキュメント
その他...
Your user tiers don't need to match between JIRA and FishEye/Crucible in order to integrate them. JIRA users that are not FishEye users will see the same view as FishEye users within JIRA, but will not be able to log in to FishEye to view the source/reviews.
From JIRA: Integrating JIRA with FishEye
From FishEye: JIRA Integration in FishEye
From Crucible: Jira integration in Crucible
From FishEye:
From Crucible: What happens if I decide to stop using Fisheye with Crucible
When FishEye is connected to 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.
Screenshots: Code changes listed in a Bamboo build (above), and viewed in FishEye (below)
Using the bundled Application Links plugin, you can configure application links with Trusted Applications authentication as well as other types of authentication.
For further instructions, please see Configuring Application Links.