Many of Atlassian’s cloud and server products provide the same benefits – planning, tracking, collaboration, code repository management, and more – but differ in features and functionality. The same logic applies to the Metadata for Confluence app.
With Atlassian’s Cloud-first plans, users moving to Confluence Cloud will also need to migrate to our corresponding cloud app.
Here’s an overview of all Metadata functionalities for Confluence Cloud vs. Server.
Please keep in mind that due to technical constraints in the cloud environment (and differing conceptual ideas in some use cases), the Metadata cloud functionalities might have some limitations.
This is the app's current state and behavior. Based on customers' requests and needs, the app can change to better meet those needs.
The main conceptual differences and how they translate from server to cloud.
|
Server Concept |
Cloud Concept |
|---|---|
|
Metadata Set |
Fields are no longer declared separately from sets. They can only be defined together. This is now called a Content Category. Content Categories can be assigned only to pages, not blog posts, and only one Content Category can be assigned to a page. |
|
Metadata Field |
|
|
Space / Global Metadata Sets |
In Cloud, only global Content Categories are available. The number of fields per Content Category is limited due to Cloud storage limitations. No fixed limit is set, as it depends on the Content Category definition. |
The main feature differences
|
Functionality in Server |
Cloud |
Notes |
|---|---|---|
|
Connect a Confluence template to a Metadata set |
|
As in the server/DC version, a Content Category can link to multiple templates, a single template, or no template. |
|
Display Metadata macro |
|
The cloud app has 2 macros named “Display Metadata” and “Display Metadata Value”. The 1st shows configurable fields and their values. The latter lets you display only the value of a Metadata field.
|
|
Metadata Overview macro |
|
In Cloud, it is renamed to: Metadata Report macro. Not all features from Server are carried over. |
|
Live filter in the Overview macro |
|
Live filter is part of the report macro. |
|
Content by Metadata macro |
|
|
|
History of Metadata values |
|
Cloud does not offer a history feature, including the History macro. We will refine it in the future based on customer requests. |
|
Text field |
|
|
|
Multi-select field |
|
Due to Cloud infrastructure limitations, we limit both field types to 30 options. In Cloud, there is no differentiation between “Dropdown” and “Radio buttons”. There is just the “Single select,” which works like the “Dropdown” on the server. |
|
Single select field (Dropdown and Radio buttons) |
|
|
|
Link field |
|
Called Page link in cloud. It only supports adding Confluence pages as values. The suggested pages can be limited by defining filters. At the moment, filters for labels and Content Categories are available. |
|
User field |
|
|
|
Date field |
|
|
|
Group field |
|
|
|
Required fields |
|
|
|
Default values |
|
|
|
Bulk change |
|
In Server/DC, it is only available for space Metadata. As there is no space Metadata in Cloud, this feature is not available. |
|
Metadata-based CQL filters for Confluence built-in macros |
|
|
|
Integration with a Workflow and document management app. |
|
There is an integration between Metadata and Appfox Workflows and Document management app. No integration with Comala document management app, as in the DC version. |
The use cases you can create with the Cloud vs Server version are still the same.
So, why should you go Cloud?
-
Atlassian’s end of support for server, as of February 2, 2024.
-
The cloud version offers easier configuration for the admins.
-
The cloud version offers better usability - specifically: Metadata values will be filled immediately in a dialogue before the page gets created.
-
The app isn’t just a toolbox anymore; it's a story creator. Use it for Process management, Project sheets, Product catalogs, Requirements, Release documentation, etc.
If you need more information to help you decide if moving from server to cloud is a good option for you for the entire Atlassian suite, check out Atlassian Cloud Migration Center.
Please don't hesitate to reach out with questions right here or set up a live product demo with one of our engaging team members.