Preload of Xray attachments does not work when Jira DC uses S3 bucket storage

If a customer is using an S3 bucket to store Jira attachments in their Data Center instance and decides to perform a migration of the Xray Preload attachment. During the migration process, when using the preload attachments option, Xray attachments are not found or preloaded as expected.

Xray Data Center supports attachments stored in S3 buckets; however, the preload attachments feature was not validated against this setup during development. At the time, we had information that JCMA did not support preloading attachments stored in S3 buckets, so this scenario was not tested. There is an existing note on the related Jira issue stating that we were waiting for feedback from Atlassian regarding S3 support.

We are currently in contact with the Atlassian team to confirm whether any changes are required on the Xray side to support this scenario. This investigation is ongoing because Jira’s preload attachments functionality does work with attachments stored in S3 buckets, which suggests that additional handling may be needed specifically for Xray attachments.

Steps to Reproduce

1. Configure Jira Data Center to store attachments in an S3 bucket.
2. Install and configure Xray Data Center.
3. Ensure Xray issues contain attachments stored in S3.
4. Run a migration using JCMA with Preload attachments enabled.
5. Observe the preload results for Xray attachments.

Expected Result

• Xray attachments stored in the S3 bucket should be correctly detected and preloaded during the migration process.

Actual Result

• Xray attachments are not found / not preloaded when attachments are stored in an S3 bucket.