Description
Atlassian Connect framework is the fundamental building block for Cloud apps going into the future of the Atlassian Cloud infrastructure. All the Atlassian Cloud users are required to either install the app or migrate it from Server to Cloud to be able to use the Markdown for Confluence app on Cloud. This page explains:
- All the aspects to keep mind while migrating from Server to Cloud
- Migration process
- Differences between the Server and Cloud version of the app
Perks of moving to Atlassian Cloud
- Delivers all the new features of Markdown for Confluence and fixes more quickly to the users. User instances automatically receive new and improved capabilities as soon as the app is formally released on the Cloud. This compares to the approach taken when the latest Server version is released, users themselves need to upgrade their instances.
- Minimizes cases or severity where Confluence Cloud updates may impact the proper behavior of the macros. While rare, we have experienced a few of these cases over the last few years that have caused customer pain. While this provides long term benefits, there are some near term disruptions.
- Allows Atlassian to deliver more significant infrastructure improvements for the benefit of all Cloud users.
Administrator's role
Nothing for the conversion. The conversion is done by Atlassian at the appropriate time for your instance as part of the rollout staging. Once your instance is converted, it is recommended that Administrators check any critical pages to ensure behavior is as expected. Please report any issues immediately after looking through the known problem list below.
...
Description
Before migrating your Markdown for Confluence app content from server to cloud, we recommend reading this Atlassian article to plan your migration.
| Note |
|---|
Administrators must ensure that the following feature flag is enabled in the server instance as a part of the pre-migration setup:
Refer to the Getting started page from Atlassian for more information about the prerequisites for the migration. |
This page explains:
- Migration process
- Differences between the server/DC and cloud version of the app
Migration process
- Confluence instance migration - Use the Confluence Cloud Migration Assistant app to migrate everything you need from Confluence
...
- server to
...
- cloud. Confluence Cloud Migration Assistant explains in detail the step-by-step procedure to migrate the required content
...
- .
- App installation - Install the app from Marketplace.
...
| Note | ||
|---|---|---|
| ||
|
| Info | ||
|---|---|---|
| ||
|
Anchor differences differences
Differences between
| differences | |
| differences |
...
server/DC and
...
cloud versions
All the macros available in the Server server/DC version are supported in the Cloud cloud version as well. The following table lists the macros' parameters and features that work differently in Server server and Cloudcloud:
| Parameter/Feature | Server | Cloud | Notes |
|---|---|---|---|
| URL whitelisting | Supported natively by Confluence and configured using the Global Configuration page | Administrators must manually whitelist the URLs in the Global Configuration page, because Confluence Cloud cloud does not natively support URL whitelisting. | For more information, refer to CLOUD-2636. |
| Rendering Markdown content having angle quotes | Supported | Not supported | For updates on this feature, refer to MARKDOWN-388. |
| Rendering links with spaces between text and link | Supported | Not supported | For updates on this feature, refer to MARKDOWN-387. |
| Linking pages to other applications using AppLinks | Supported | Not supported | For updates on this feature, refer to MARKDOWN-375. |
| Exporting a page as an attachment, or, in as a PDF or Word formats | Supported | Not supported | For updates on exporting a page as an attachment feature, refer to MARKDOWN-216. For updates on exporting a page in PDF or Word formats feature, refer to MARKDOWN-264. |
| Using customized CSS for tables in macros | Supported | Not supported | For updates on this feature, refer to MARKDOWN-261 |
Please note that all the other parameters function the same in both versions of the app.
Problem reporting
If you experience any problems or behavior changes that are unexpected, refer to Help and open a ticket with us. This helps us identify and prioritize fixes and improvements.
Known issues
Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = MARKDOWN AND issuetype in (Bug, Improvement, "New Feature", Story, Task, Sub-task) AND status in ("In Progress", Open, Queued) AND component = cloud serverId 729d679a-302c-339f-958b-015e107badcd