When a production-to-sandbox data copy fails in Jira Cloud, customers receive only a generic "Unable to copy data into your sandbox" email notification with no actionable detail about what went wrong or where the process failed. This forces customers to contact Atlassian Support for every failed copy attempt, creating unnecessary friction and support overhead.

What Currently Happens:

 1.  Customer initiates a sandbox data copy from admin.atlassian.com → Products → Sandboxes → Copy production data
 2.  The copy process begins and shows "Copying data..." in the UI
 3.  If the copy fails at any point, the customer receives a generic email: "Unable to copy data into your sandbox"
 4.  The UI provides no additional error detail, no indication of where the process failed, no partial success information, and no suggested remediation steps
 5.  The customer is left with no choice but to contact Atlassian Support to investigate backend logs - which they have no access to

What Would Be Nice to Have (Desired Behavior):
Similar to how Jira Cloud CSV imports handle failures - where a detailed log file is generated and made available for download showing exactly what succeeded, what failed, and why.

Sandbox data copy failures should provide customers with:

 1.  A downloadable error log generated at the point of failure, showing:

•  Which stage of the copy process failed (e.g. projects, users, attachments, automation rules)
•  How much data was successfully copied before the failure
•  The specific error or exception that caused the failure
•  Any data that was skipped or partially copied
 2.  An improved failure notification email that includes:

•  A summary of what was and wasn't copied
•  A direct link to download the error log
•  Suggested self-service remediation steps where applicable (e.g. "Your copy failed due to attachment size limits, consider using the 'Copy without attachments' option")
 3.  An in-UI failure summary in the Sandboxes section of admin.atlassian.com showing the last copy attempt status with a brief error reason, not just a spinner that disappears

Why This Matters:

•  Sandbox data copies can take hours - customers invest significant time and have no visibility into why it failed
•  Without error details, customers cannot self-diagnose or attempt a targeted retry (e.g. trying without attachments if the failure was attachment-related)
•  Every sandbox copy failure currently requires a support ticket, increasing unnecessary support load
•  The CSV import failure log precedent already exists within Jira Cloud - this is a natural extension of that pattern to sandboxes

This looks to have also already been possibly shipped for Confluence, but not for Jira cloud.