Downloads (PDF, HTML & XML formats)
[FishEye Knowledge Base]
You can integrate FishEye with the following Atlassian applications:
When FishEye is integrated with JIRA , you can: See User management limitations and recommendations. When Crucible is integrated with JIRA, you can:
Your user tiers don't need to match between JIRA and FishEye/Crucible in order to integrate them. | When JIRA is integrated with FishEye, you can: | |
When FishEye is integrated with Crucible, you can: In FishEye:
In Crucible:
See also What happens if I decide to stop using Fisheye with Crucible. You'll need the same number (or higher) of users in FishEye as Crucible. | ||
See: | ||
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. |
Screenshots: Code changes listed in a Bamboo build (above), and viewed in FishEye (below)
A 'trusted application' is an application that FishEye will allow to access specific functions in FishEye on behalf of any user, without the user logging in to FishEye. You can configure Trusted Applications authentication between FishEye, Crucible, JIRA (3.12 and later) and Confluence (2.7 and later).
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.