Migration to Bodied Macros (Cloud → Cloud)

Recent Changes

Table Enhancer was previously implemented as a non-bodied macro that would enhance a table located somewhere else on the same page.

With the latest updates to the Atlassian Forge platform, we can now support bodied macros for Table Enhancer. This means the table you want to enhance is now enclosed within the Table Enhancer macro, instead of being outside it.

To ensure a smooth transition, we’ve introduced an automatic migration path. Although you can no longer create the old configurations, they will continue to function for the time being.

Automatic Migration

We automatically scan all pages containing a Table Enhancer macro and convert these setups by incorporating the referenced tables into the macro body, and removing it from the old location.

This process is designed to minimize both resource strain and service disruption on your instance. You may notice updates made by the App in your feed. For troubleshooting purposes, we generate logs that can be accessed when you contact us for support.

Manual Migration

For manual migration, simply create a new macro, copy the relevant table into it, and delete the old macro.

Troubleshooting

If the automatic migration encounters issues, you can revert to a previous version manually and handle the migration yourself.

Be aware that the App might not identify every page with a macro due to permission settings. In these cases, a manual migration will be necessary.

If you have any remaining issues, please don’t hesitate to reach out to us and open a ticket at our service desk. We are happy to assist!