Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-1510

Link Fixing doesn't fix Confluence "Content by label" macro

XMLWordPrintable

    • 9
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      After the Server to Cloud or Cloud to Cloud migration Confluence "Content by label" macro are not getting fixed.

      Example macro:

      <ac:structured-macro ac:name="contentbylabel" ac:schema-version="3" ac:macro-id="{macro_id}"><ac:parameter ac:name="showLabels">false</ac:parameter><ac:parameter ac:name="max">500</ac:parameter><ac:parameter ac:name="showSpace">false</ac:parameter><ac:parameter ac:name="sort">title</ac:parameter><ac:parameter ac:name="cql">label = &quot;{label}&quot; and parent = &quot;{contentid}&quot;</ac:parameter></ac:structured-macro>
      

      contentid is the old contentid migrated from Server or Source Cloud instance.
      It has to be replaced with a corresponding new contentid of the Destination Confluence Cloud.

      Suggested Resolution

      Confluence "Content by label" macro should be updated post migration:

      • replace server/source cloud contentid with destination cloud contentid

      Temporary Resolution

      Contact Atlassian support by logging a request in support.atlassian.com and ask them to apply the workaround for this issue.

      Team will apply a workaround under the boundaries of https://confluence.atlassian.com/confkb/legacy-link-fixing-after-a-successful-server-to-cloud-migration-url-links-are-broken-in-the-new-cloud-instance-1271267903.html to fix the problem. 

              06eb947e2f93 Łukasz Halicki
              f4a240011bb9 Anatolii Kostin [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: