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

App migration fails from 403 errors from calling migration APIs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • CCMA - 3.10.13, JCMA - 1.12.23
    • Apps - Migration Assistant
    • None
    • 1
    • Severity 2 - Major
    • 7
    • Hide

      We are gathering impact

      Show
      We are gathering impact

      Issue Summary

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Create a plan in JCMA or CCMA with apps that have an automated migration path
      2. Start migration 
      3. Remove your use from site admins in target cloud site
      4. JCMA or CCMA will start throwing 403s and app migration fails

      Expected Results

      JCMA and CCMA can gracefully handle scenarios when users temporarily lose site admin access

      Actual Results

      App migration hard fails. Example logs in this scenario

      com.atlassian.jira.migration.httpclient.exceptions.UnexpectedStatusCodeException: Received an unexpected status code; expected [200], but received 403: {"timestamp":"Feb 13, 2025, 7:01:30PM","status":403,"error":"Forbidden","path":"/api/migration/upload/url"}
at com.atlassian.jira.migration.httpclient.exceptions.ExceptionsKt.unexpectedStatusCode(Exceptions.kt:9)
at

      Workaround

      Ensure there are no automation rules that may temporarily remove site admin access for the user performing the migration

            [MIG-2202] App migration fails from 403 errors from calling migration APIs

              Unassigned Unassigned
              6ec6a48ca208 David Yu
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated: