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. |
...
Info | ||
---|---|---|
| ||
|
...
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 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, 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.
...
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