Confluence Miro Import UI instructs users to enter Space ID from dashboard URL, but Miro API requires numeric Project ID (causes failed imports)

XMLWordPrintable

    • 1

      Issue Summary

      When using the Confluence Miro bulk import feature, the UI instructs users to copy the Space ID from the Miro dashboard URL (e.g., /space/1MuWIQTTGB62RODzuk31FO). However, Miro has recently renamed "Projects" to "Spaces" in their UI and now uses an alphanumeric slug in the URL for routing. The Miro API still expects the original numeric Project ID for the project_id parameter.

      This mismatch causes the import to fail with a 400 Bad Request error from the Miro API, as the alphanumeric slug is not accepted. Users following the UI instructions are unable to complete their imports.

      Steps to Reproduce

      1. Go to the Confluence Miro import page.
      1. Follow the UI instructions to copy the Space ID from the Miro dashboard URL.
      1. Attempt to import boards using this value.
      1. Observe that the import fails with a 400 error.

      Expected Results

      The UI should instruct users to provide the numeric Project ID required by the Miro API, or provide a way to retrieve it easily.

      Actual Results

      The UI instructs users to enter the alphanumeric slug from the URL, which is rejected by the API.

      Workaround

      • Open any board in the target space in Miro.
      • Copy the Board ID from the URL.
      • Find the numeric "id" under the "project" object in the JSON response.
      • Use this numeric ID in the import UI.

              Assignee:
              Unassigned
              Reporter:
              Abhinay Nigam
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: