Integrate Jira Cloud with Jira Server

Still need help?

The Atlassian Community is here for you.

Ask the community

This page includes details about integrating Jira Cloud with Jira Data Center or Server.

In summary

(tick) Linking issues between instances Show

(tick) Using Jira Server’s activity stream in Jira Cloud Show

(warning) Using Jira Cloud’s gadgets in Jira Server (with the exception of the ones related to sprints) Show

(error) Using Jira Server’s gadgets in Jira Cloud Show

(error) Combining data from linked instances Show

(error) OAuth with impersonation Show

In-product integration

None


The following features are available when you link your products with application links. Unless clearly stated, they are available for all Jira applications: Jira Work Management, Jira Software, Jira Service Management.

Linking issues between instances

You can link issues between Jira instances (from both sides). We’ll use linking from cloud to server as an example:

(info) You can’t link to an issue that has the same issue key. Jira Cloud will see that as linking the issue to itself, even if you selected and searched the remote instance. Such a link will work if you create it from Jira Server.

If you choose to create a reciprocal link, your cloud issue will also be added to Jira Server.

Using Jira Server’s activity stream in Jira Cloud

You can use the activity stream gadget in Jira Cloud. Remaining gadgets aren’t supported as you can’t register them in Jira Cloud.

Using Jira Cloud gadgets in Jira Server

You can use Jira Cloud gadgets in Jira Server after registering them.

(warning) Gadgets related to sprints won't work. You can add most of them, but they won't show any data.

Unsupported features

Using Jira Server gadgets in Jira Cloud

Jira Cloud has deprecated the option to register external gadgets, so you won’t be able to add any external gadgets from Jira Server.

Combining data from linked instances

Application links allow your instances to exchange features created specifically for integrations (issue links in this case) or see the linked instance as a remote application (which can be used by Marketplace apps to provide more features), but your instances are still separate instances. As such, they don’t provide the following features, which are often expected:

  • Searching between instances

  • Creating a board that includes issues from linked instances

  • Syncing duplicated issues between instances

There are some Marketplace apps that provide some of these functionalities.

OAuth with impersonation

OAuth with impersonation is one of the authentication types in application links. It has been deprecated in Atlassian cloud products and can’t be used. You can only use OAuth without impersonation.

Features available through in-product integrations

There are no additional in-product integrations available for this combination of products.

Integrate these products

To create the application link, see Create application links.

Last modified on Jun 7, 2023

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.