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
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

754 views 2 19
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