Hi

This is in closed beta, please fill this form and we can enable this feature in your instance. https://aianswers.atlassian.net/servicedesk/customer/portal/5/group/13/create/47

thanks

joe

Hi Guys,
Is there any update on this issue. 

We have different domains for our Jira & Confluence. We cannot use the knowldgebase for our JSM. 

Kindly resolve this issue asap.

Hello 6cf75f652d57, any updates on the EAP? Will this be available to everyone in the near future?

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

We'd like to take full advantage of Atlassian Intelligence. However, our primary KBase is in a Confluence site that is outside of our ISM site. It would be immensely valuable to be able to link the KBase of the JSM project to our Confluence KBase that exists in our other site. 

Or at least provide a workaround to allow this functionality. 

Please make this feature available, for seamless integration between cloud instances for the same organisation/client.

Hi, This feature would be great to have because more and more clients are moving through instances and they need to have one KB for all instances and not only for the one that conflu was created on. Please make that possible Atlasssian.

We have separat URL instances for jira, confluence and JSM. Please make this feature available to connect JSM KB to different site url.

We also affected by the same that Philip mentioned. We're trying to move to Cloud from a 2000 user Server Confluence  (Jira Server  Service Desk) and the connection is very important for us. The lack of this option is.. let me say an "almost showstopper" for us regarding the moving process.

we also have the same issue.

our teams have separate instances of Jira / JSM (mostly for permission issues) but would like to leverage the same confluence instance for knowledge base. 

seems wasteful and inefficient to pay for 2 confluence cloud (and all the users) and split up our knowledge base.

We would find this very valuable, as I commented in the duplicate ticket at https://jira.atlassian.com/browse/JSDCLOUD-8335)

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?

We have Atlassian Access and manage three cloud instances under the same umbrella.  Different help centers with different use cases that have different internal user-provisioning (two are G Suite, one is Okta).  We were hoping that we would not have to set up an entirely new Confluence instance for our newest Jira instance since we could leverage our existing internal knowledge base for everyone.  Didn't realize the application link functionality between instances was deactivated.

I will try to workaround this by setting up a bare-bones instance, but just wanted to document this use-case as I said I would on a support ticket.

This is important feature. For some of the clients, the Jira and Confluence are managed by different teams and can not be moved/migrated at the same time.