Impact on Content links when dropping the port for accessing Confluence

I'm curious what the impact of correctly configuring Confluence (SSL, eliminating the port, etc.) will have on linked Confluence pages in JIRA issues.

Not having a clear understanding of Confluence, etc. when we deployed and being under the gun, we proceeded with basic configuration via the port... i.e. http://confluence.ourdomain.com:8090/confluence.

My goal is to correctly configure Confluence to use Apache for caching, eliminate the unecessary port, and trailing directory. The catch is that I have an Application link between JIRA and Confluence and want to be sure that if I change Confluence, I'll be able to maintain the application link without breaking things between the two applications.

If there's additional work to do to achieve this, I'm fine with that as well, but I'd like some advice on making this change with minimal breakage on the existing content in JIRA/Confluence.

Advice is appreciated.

1 answer

Anyone with some experience here?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

20,889 views 2 7
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you