Issue Summary

In Jira Cloud, attachments (images, videos, etc.) uploaded directly into a rich-text custom field appear to be "owned" by that specific field rather than the issue itself. If the content of this custom field (ADF) is copied to another field (such as the native Description field), the media references are preserved and the files remain visible.

However, if the original custom field is subsequently deleted, all attachments originally associated with it are also deleted from the media store. This occurs even if those attachments are still actively referenced and displayed in other fields on the same issue.

This behavior is silent and destructive, as there is no warning during the field deletion process that it will impact media displayed in other fields, and the deletion of these attachments is not recorded in the issue history or audit logs.

Steps to Reproduce

1. Create a rich-text custom field (e.g., "Original Field").

1. Create a Jira issue and upload an image/video directly into "Original Field".

1. Copy the content (ADF) of "Original Field" into the native Description field.

1. Verify the attachment is visible in both fields.

1. Delete the "Original Field" custom field (and purge it from the trash).

1. View the issue and check the Description field. The attached file will be with a "preview unavailable" error and can't be retrieved.

Expected Results

The attachment should remain available because it is still referenced by the Description field. Jira should recognize that the file is still in use.

Actual Results

• The attachment is permanently deleted from the issue and the media store.

• The Description field shows broken media blocks (404 errors for the file IDs).

• No record of the attachment removal appears in the issue history.

• No warning is provided during the custom field deletion flow regarding the loss of these files.

Workaround

There is no known workaround to prevent the deletion once the field is trashed. Users must manually download and re-upload all attachments to a different field before deleting the original custom field to ensure the issue "owns" the new file reference.