Using non-DC compatible apps in Data Center instance

Cross Product Knowledge

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible


When migrating to Data Center instance, Atlassian app (Jira/Confluence) will compile a report of all third-party apps that are not marked as DC-compatible. See below on possible action items for such apps.


For every app marked as non-DC compatible, the following action items should be considered:

  • Check if a newer app version marked as DC-compatible available at Atlassian Marketplace.
  • Contact the app vendor directly and inquire whether the app can be used in Data Center instances of the specific Atlassian app you want.
  • If you don't get any response from the vendor, you can still use the app in DC instances, though it may not operate partially or fully. See below for detailed explanation.

Information on apps marked as non-compatible in Data Center

The main issue with apps marked as non-DC compatible by Jira/Confluence is a plugin cache, which in DC case is getting replicated between nodes. If the app is non-DC compatible, its cache will be inconsistent between nodes, which may affect the plugin performance and operation. To what extent this can affect the plugin it is difficult to say - it solely depends on the app usage of the cache. In some cases, this will not affect the app at all.

If the app vendor is not responding, you can still install the app in the DC environment and observe its functioning. Some plugins may not require any functionality changes to make them DC-compatible, it is just they were never checked and flagged as DC compatible by their vendors.

Last modified on Jan 22, 2024

Was this helpful?

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