Fisheye references old Jira instance when accessing Jira issues
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Whenever clicking on Jira issues links on Fisheye, no matter what comment, project, commit, etc, they are all linked to the wrong Jira server instance.
This happens when having Fisheye integrated with two or more Jira instances via Applications Links. To have a better understanding of the issue, we will reference the instances as:
- new Jira instance (it is set as the Primary instance)
- old Jira instance
The Jira instances can be Cloud or On Premise.
Diagnosis
You may want to perform two different tests to reproduce the issue:
- delete a project from the old Jira instance that was already migrated to the new Jira instance
- remove the old Jira instance ApplicationLink
In both tests, Fisheye still tries to connect to the old Jira instance, even though the issue not existing there anymore OR with the Application link undone.
Environment
Fisheye integrated with two or more Jira instances via Applications Links.
Cause
Reviewing the config.xml file we see the following section:
<linker><simple regex="[a-zA-Z][a-zA-Z0-9]+-\d+" href="https://<<OLD_JIRA_URL>>/browse/${0}" description="JIRA issue link"/></linker>Linkers is a feature to render any issue IDs or Bug IDs that appear in commit messages or comments as hyperlinks.
This feature is enabled on Fisheye instance for all repositories and it's also referencing the old Jira instance base URL. This is causing Fisheye to redirect all the Jira issues to the old Jira instance instead of the new one.
Resolution
Go to the Linkers section in UI and completely remove the configuration.