Issue Summary

During an attachment upload (Jira Cloud Migration Assistant), Atlassian's Cloud Media API returns HTTP 503 on POST /file/binary.

Steps to Reproduce

1. Use JCMA to migrate Jira project and attachment data
2. Jira data will upload successfully
3. Jira attachment upload will fail (sometimes at 99%)

Expected Results

Attachment upload should complete successfully if there are no issues with the source export/upload. Atlassian's Cloud Media API should improve handling of 503 responses.

Actual Results

The exception below is thrown in the atlassian-jira-migration.log:

Received an unexpected status code on executing HTTP POST to https://api.media.atlassian.com/file/binary?... expected [201], but received 503 

Workaround

The workaround depends on the migration phase in which the failure occurs:

• If the issue occurs during Attachment Preload:
  • Option 1 (Retry): Re-run a new attachment preload, specifically selecting the failed/incomplete project(s).
  • Option 2 (Proceed to Full Migration): Proceed directly with the full Jira data migration. The migration will automatically perform a delta check and transfer any remaining or missed attachments.{}
• If the issue occurs during Full Jira Data Migration (Project Data + Attachments), there currently is no workaround (MIG-301):
  • If the core Jira project data succeeds but the attachment upload step ends INCOMPLETE or failed, JCMA does not currently support running an attachment-only migration for already migrated projects.
  • Action: Please contact Atlassian Support for assistance in verifying attachment integrity on Cloud. However, the JCMA tool will not be able to relink any attachments that are migrated AFTER Jira project data has been migrated.