Content Formatting Toolkit for Confluence

내용에 테이블을 넣으면 보이지 않습니다.

Lost valuable data because of on-prem to cloud migration. The cloud version is different and doesn't support the same data we had on-prem.

• 

  VECTORS

  [UPDATE]

  Hello Chris,

  Migration path for App from Server to Cloud is operational and Apps data can be migrated via CCMA since few months. Sorry for not updating the message.

  All details about macros parity, management of legacy mode and documentation can be found in this link

  We remain at your disposal via our support portal for any information needed about migration.

  Thanks

  ===============================================================================

  Hi Chris,

  Thanks for your feedback. For the time being, on-prem to cloud migration for Spectrum Formatting Macros cannot be done manually as the app is different across the three hosting options. Additionally, Atlasian’s new editor does not support nested macros thus the loss of data. Our product team is fully aware of the situation and we are fully committed to provide an optimal application, a clear migration process and tool as well as move towards complete parity in the near future. We will let you know once the fix is available.

  Feel free to reach out if you have any questions.

  Many thanks

Spectrum Formatting Macros worked well on Confluence Server, but after migration to Cloud we have encountered several issues: 1. No support, solution or any workaround for nested body macros such as: vertical-nav-item & vertical-nav-group horizontal-nav-item&horizontal-nav-group tab-pane & tabs-group 2. SP Page Status Macro is set to Draft the first time the page is displayed, after it has been migrated to Cloud, by the user who first viewed the page. 3. The SP Page Status Macro shows the time in GMT, regardless of user's profile or global Jira timezone For getting support before and after the migration, we have opened two tickets for support, where we did not receive any hint or suggestion on how to fix thousands of pages affected, and no evidence that there is any bug opened to fix those issues. The communication was poor We hope that these issues can be more transparent in the future, so that customers would know what to expect when migrating their instance to Cloud.

• 

  VECTORS

  Hello Mihaela,

  Thanks for your feedback. We completely understand your frustration, as migration can become a very tedious process, especially in the absence of the adequate tools and assistance. Perhaps there has been a lack of constant communication from our end, but for the last couple of weeks our team has been working on finding a solution to Atlassian non-support of nested macros. Our support made its best to assist you in the raised support request and explain that unfortunately there is no workaround possible, and we need to find a solution via custom development during the migration process. Following the migration path will allow you to avoid any bugs you have already encountered and enjoy a similar experience to Spectrum Formatting Macros on server.

  We will let you know when the migration path is available (We expect the potential solution found to be landing in the marketplace before the end of the Month). In the meantime, please make sure to contact our support team. We are happy to hold a call with you to discuss issues and find workarounds together.

  Thanks for your understanding.