We have a subversion repository mapped into the plugin like this:
https://ourserver.us.co.uk:8443/svn/java and we want to use fisheye for web linking. However fisheye projects do not use the subversion project name as a project name. So for example our fisheye project may be 'not_unix', while the subversion repository project is called 'gnu'. So when a changeset is picked up the subversion plugin tries to link to fisheye using url:

http://ourserver.us.co.uk/fisheye/viewrep/gnu/branches/mybranch/a?r=123
but fisheye responds that the project was not found at that location - since it is using mapped project names (the names are different to the svn repo) and would instead expect us to look in:
http://ourserver.us.co.uk/fisheye/viewrep/not_unix/branches/mybranch/a?r=123.

So - we need to be able to use the fisheye mappings for a project from subversion in the subversion plugin - i.e. either replicate the same behaviour in the svn plugin that exists for fisheye- or allow bi-directional mapping in fisheye for projects from project name or subversion project name?