Atlassian encourages migrating customers to from DC to Cloud and developers to Forge.
However, for Confluence macros the migration from DC->Cloud with Forge is harder / breaks the migration, at least as far as we can tell.
There are 3 issues I’ve noticed: Missing hidden macros, the missing legacy editor support and strange layout behaviors.
-
Missing ‘hidden’ macros: We used a ‘hidden’ macro in the Connect app to support migrated pages. The idea is to still show migrated content, but disallow creating new content with the in the ‘DC style/configuration’.
So, we need either:- Have some alias functionality, to support the old ‘DC macro’ key and use the same macro.
- Or Still have a way to mark a macro as hidden. To avoid confusion an dissallow creating ‘old DC style’ macros.
This seams missing, or am overlooking this options in the documentation.
-
When migrating a page from Confluence DC → Cloud, it starts of in the ‘legacy’ editor. In the legacy editor, the Forge macro is not shown! So, it does look like the migration failed / the macro is broken. Only converting the page to the new editor will reveal the macro.
-
Once the page is converted to the new editor, the macro does show up. However, it has a weird narrow layout. Only coping, deleting and pasting the macro in seems to fix the layout. Not clear to me what causes this odd layout.
The summary: At the moment it seems that we have to keep the ‘migration support’ macro on the Connect side. However, that won’t last long, as we do not want to support a extra Connect edition of the macro for the migration.
So my hope:
- These issues get fixed?
- There is some other way to support the migration without large efforts.
