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

Link fixing doesn't fix the attachment links added using API.

XMLWordPrintable

    • 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.

      The customer uses the REST API to create the page and add attachments to it. However, after migration, the attachment preview doesn't load because the page ID is using the IDs from the server environment. The storage format for the attachments is as follows:

      <p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" height="250" src="/download/attachments/115348860/_duration.png" /></span></p>
      

      Steps to reproduce:

      1. Create a page and add attachments using the REST API in the server instance.
      2. Ensure the storage format is created as mentioned above.
      3. Migrate the space using the CCMA.
      4. After migration, the attachment preview does not load.
      5. Run the link fixing tool; however, it fails to fix the attachment preview.

      Expected Behavior:

      The link fixing tool should update the contentid and direct it towards the cloud instance.

      Actual Behavior:

      Link fixing tool doesn't fix the attachment preview.

              Unassigned Unassigned
              54bf2707b706 Deepak Pandey
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: