Application link Alias

Currently, an applcation link can only have one instance to each server it link to.

However, when importing spaces from external Confluence instance pointing to external Jira instance that are also imported, all the application links will point to the old instance, breaking every macro using that link.

The fix suggested mention editing and saving the affected macro, but when you have hundred of macro, this is not a viable option.

The alternative is to go into the database and rename every occurrence of the old link and replace ti with the new name.

By allowing Application Links aliases, one could create an alias using the old link name and all macro would still work.

This also apply to Jira macho, which utilize the Application Link name to references which Jira instance to use. Should the application link be renamed or imported with a different name, they will all break.

Editing the macro will fix it, but in the case of a voluminous space, this can be impossible unless manually converted inside the database while Confluence is offline.