Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Duplicate
Priority: Low
Fix Version/s: None
Affects Version/s: 5.4.2
Component/s: Integrations - Jira
Labels:
- affects-server
- jira-integration
Environment:

Hide

Stand-alone Confluence 5.4.2, Linux 64-bit installer
Stand-alone JIRA 6.1.7, Linux 64-bit installer
CentOS
Test environment

Same server, separate directories, separate ports, two ports for each, SSL termination for one port and not for the other, Application URL points to unsecure port, Display URL points to secured port via reverse proxy

Show
Stand-alone Confluence 5.4.2, Linux 64-bit installer Stand-alone JIRA 6.1.7, Linux 64-bit installer CentOS Test environment Same server, separate directories, separate ports, two ports for each, SSL termination for one port and not for the other, Application URL points to unsecure port, Display URL points to secured port via reverse proxy

Bug Fix Policy:
View Atlassian Server bug fix policy

Description

In stand-alone Confluence, with an Application Link built to stand-alone JIRA, where the Application URL is different from the Display URL, the link in the Navigation Bar to go to JIRA incorrectly uses the Application URL, rather than the Display URL.

In JIRA, the same link built the same way pointing back to Confluence uses the Display URL - which is the desired behavior.

In our environment, both JIRA and Confluence are behind an SSL terminator - they can talk to each other without SSL, but users cannot reach them on the same ports they use to communicate with each other (both have two entries in servers.xml, and are listening on two ports each). This seems to work great in every respect except for the link on the Navigation Bar from Confluence to JIRA.