For testing purposes a Fisheye 2.8.2 installation was made, some Fisheye repositories were defined and connected to our JIRA instance. This was working fine. The decision to go productive was taken and a complete new Fisheye 2.9.1 installation (no upgrade!) was performed. As soon as the application link from JIRA to the new Fisheye instance has been estableshed the old Fisheye entitiy mappings reappeared in JIRA. This although all mapped JIRA projects and Fisheye repositories had been removed before Fisheye 2.9.1 had been installed. This mappings are still somehow active in JIRA: activating the 'source' tab in our JIRA projects shows error messasges ('The requested resource cannot be found')
You probaly have some application link or the project links still configured from the old version on your JIRA application.
Please verify the Application Links screen and the Project Links on each project administration screen for any links that may be causing this.
Also, try refreshing the cache on your Fisheye configuration screen (on JIRA) just to make sure only the new repositories are synched.
Hope this helps,
Thank you Marcus
I've checked the project links of all my JIRA projects: there are no links configured.
In the meantime I have carried out the following actions (from atlassian support) but they did not solve the problem:
These 3 actions require you to shut down your instance first.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs