-
Bug
-
Resolution: Fixed
-
Medium
-
3.0.0, 3.0.1
-
None
When creating an Application Link to another instance, Fisheye will populate the Application Navigator automatically using the Application URL instead of the expected Display URL.
This creates a problem when the App URL is an internal reference to a system, such as http://localhost:port. Fisheye may be able to contact the application with that URL, but the user cannot, and will most likely see a site unreachable message.
Workaround:
1) Hide the existing (automatically generated) App Nav entry using the Hide checkbox.
2) Create a new app link manually using the display URL.
- is related to
-
CONFSERVER-29142 Application Navigator uses Application URL instead of Display URL from Application Link
-
- Closed
-
-
BSERV-3687 Application navigator use wrong URL
-
- Closed
-
-
ANL-30 Failed to load
- is caused by
-
ANL-3 Failed to load
- mentioned in
-
Page Failed to load
The correct fix for this problem is not to use the display URL from the application link. It is for navigation links to use the Base URL of the application – the application itself knows at which URL it is visible, and this should only need to be set in one place (that app itself) not in various application links which point to it.
This problem needs to be fixed in each application – The link to JIRA, for example, is provided by JIRA. This bug (
FE-4698) covers making FishEye/Crucible provide a correct URL to the navigation links displayed in other applications, and doesn't cover displaying correct navigation links to other applications in FishEye/Crucible. See this issue's 'Related Issues' for issues in other applications.