Hi,

I'm Joseph, the Product Manager leading the development of this feature that allows you to link Confluence spaces from different sites within the same organization. We're excited to offer this in an Early Access Program (EAP) to a select group of customers. If you're interested, please take a moment to review the benefits and limitations of the EAP version and fill out the form to apply.

We are releasing this early access program to learn from your feedback and prioritize the remaining items for this feature. We would appreciate your feedback. 

joe

Hi 6cf75f652d57,

I just noticed the AI feature has been activated for our JSM portal. Now we would only need to have a way of linking our documentation from our separate Confluence instance. Is there a guess on when this will be possible?

Hi

I am Joseph, the PM working on this feature. We are now exploring solutions and would like to validate our thinking with a few of you to make sure we are building the right solution. If you are willing to have a 15 min call regarding this, please use this link and set up a call with me.

cheers
joe

should be standard, otherwise usability is pretty limited

+1

Trying to connect our Prod Confluence to Jira Sandbox - seems like a no brainer you'd want this to be doable for testing purposes so it's a "like to like" environment for our Prod Cloud instance.

The fact it was originally possible but was reversed in 2017/2018 sounds more like Atlassian forcing customers to require a premium license for both products so both have sandbox instances.
Our Confluence instance doesn't not see a lot of major change so a full Confluence sandbox environment isn't really necessary for our needs.,

would be a useful feature for those organisations that manage multiple Jira Cloud instances

Additionally this issue seems to duplicate JSDCLOUD-5782, which has a few more votes/watches.

We are currently evaluating JSD Cloud for our customer facing help desk, and we'd find a lot of value in being able to provide a KB alongside the support portal. In fact the driving reason behind our evaluation of JSD is the integration with our existing Atlassian tooling. We are/will be running JSD on a distinct domain/site, but are paying for Confluence under our main site. It's problematic that while we can create an AppLink between JSD Cloud and Confluence Cloud, we can't use that to provide a KB to customers from our existing Confluence Cloud site.

It appears based on Atlassian's own documentation and related issues that this was once possible but the capability was removed:

December 2017 blog post from Atlassian: "Knowledge bases must be on the same domain as your service desk".

Related JSD Cloud ticket from that blog post: JSDCLOUD-5782

Related Confluence Server ticket from that blog post (filed under JSDCLOUD): JSDCLOUD-5783

Update from October 2018 where Atlassian announces EOL for this feature: "Update: Knowledge bases must be on the same domain as your service desk".

It would be great to have this back! Can Atlassian at least shed more light on why this feature needed to be deprecated?

Hi,

We have been using Confluence for several years, and now starting to use Jira Service Desk (both Cloud sites). 
What we are expecting is that our existing Confluence could be used as the knowledge base for Jira Service Desk, not to create a new Confluence site.

Or, at least the knowledge base Confluence should not cost additional license if user already have a license for another Confluence site under the same Organization.