Fisheye-Crucible integration does not work after upgrading to JIRA 4.3

Still need help?

The Atlassian Community is here for you.

Ask the community


After upgrading to JIRA 4.3, Fisheye/Crucible integration does not work. For example, when viewing an issue's changesets you will see errors saying "unknown repository XXXX". A sure symptom is that the repositories in these error messages will not be repositories that are mapped to the JIRA project.

Screenshot of the error (click for full-size image)


This potentially happens if the configuration data between the plugin and the application link is out of sync, and the upgrade process was unable to re-sync them. This happens when there are two or more Fisheye instances mapped prior to the upgrade to JIRA 4.3, and those Fisheye instances used the same Server ID.


Go to the 'Fisheye Administration' page in JIRA and click the 'Refresh' link. This will cause the plugin to attempt to re-sync between Application Link and its internal configuration.

Screenshot of Fisheye Administration page in JIRA (click for full-size image)

If clicking on the refresh link did not work, please contact Atlassian Support for further assistance.

Last modified on Jul 31, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.