After migration, the page with lots of statuses has lower performance. 

As every Handy Status or Handy Date macro is implemented as an iframe in Confluence Cloud, the performance of the page can be affected. This number of iframes loads your browser and causes a time delay in page loading. Some additional factors can affect the speed of loading. 

After migration, the Handy Macros page in the Apps section fails to load.

This issue can be caused by the fact that the app doesn't have enough permissions to perform the user permission check. 

The root cause of this issue is that the atlassian-addons group, to which the Handy Macros for Confluence app is a member, doesn't have product access to Confluence. Thus, even though the Handy Macros for Confluence app has the required permissions, it couldn't get to Confluence.

That said, the Atlassian Support Team needs to be contacted to add the atlassian-addons group with product access to the affected Confluence Cloud site.

After that, the Handy Macros for Confluence app will operate as expected.

After migration, the Handy Macros page in the Apps section fails to load, and Handy Statuses are unavailable on pages.

Previous migrations to the current Cloud host can be the root cause of the issue.

When you delete any status set from the Manage apps section, sets and statuses are marked as deleted and hidden from the app UI. However, their entries are still stored in the DB. It leads to the fact that when you run another migration, statuses and sets are not created (as they still exist in the DB). This type of implementation has been selected, as the app can't know which Confluence spaces and pages have certain Handy Statuses.

We suggest:

  • Delete all Handy Status data on your Confluence host using our recently added feature available to Confluence Administrators. Please see the documentation about it.
  • Re-run the migration to this host. You need to migrate only Handy Macros for Confluence with any empty or small Confluence space. No need to re-run all spaces.

Unable to install the app

This issue can occur when you are trying to install or reinstall an app from the Atlassian Marketplace. In the UI, you will get the message saying, 'We ran into a little trouble. It might just be a hiccup'.

This is a known issue that eventually occurs. To troubleshoot it, please, contact the Atlassian Support Team. You can also let our support know about this issue to add us as participants to your Atlassian ticket for any assistance if required.

How do I distinguish between global, space or personal status sets after migration?

On Cloud, all the sets will appear in one storage without division into categories. For your better navigation among them, set names will get some prompts regarding their origin. Global sets will retain their names, space sets will get the name format "SET_NAME space(SPACE_KEY)", and personal "SET_NAME personal (ATLASSIAN_USER_ACCOUNT_ID)".