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')