Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-32033

Application link Alias

XMLWordPrintable

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      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.

            [CONFSERVER-32033] Application link Alias

            Sen Geronimo made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3574688 ] New: JAC Suggestion Workflow 3 [ 4335975 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3179349 ] New: JAC Suggestion Workflow 4 [ 3574688 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3038868 ] New: JAC Suggestion Workflow 2 [ 3179349 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2536607 ] New: JAC Suggestion Workflow [ 3038868 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2300970 ] New: Confluence Workflow - Public Facing v4 [ 2536607 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2197796 ] New: Confluence Workflow - Public Facing v3 [ 2300970 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1939201 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2197796 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1754746 ] New: Confluence Workflow - Public Facing v3 [ 1939201 ]
            jonah (Inactive) made changes -
            Description Original: 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.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-32033].
              {panel}

            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.
            jonah (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-32033 [ CONFCLOUD-32033 ]

              Unassigned Unassigned
              49380b3a1ecf Philippe Busque
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: