-
Type:
Bug
-
Resolution: Tracked Elsewhere
-
Priority:
High
-
Component/s: Issue - Backend
-
2
-
Severity 3 - Minor
-
Warranty
Issue Summary
When cloning an issue, if the "Attachment" checkbox is unchecked, the clone will still include the attachment file if the attachment in the original issue belongs to a parent_field. For example if the attachment is uploaded into the Description field, or a custom field.
Steps to Reproduce
- Upload an attachment into an issue's custom field. For example - copy and pasting an image into the Description field, or any other custom field that allows attachments.
- Clone the issue and do not enable the "Attachment" checkbox

- The cloned issue still includes the attachment because the Clone feature is copying all customFieldValues.
Comparatively, if the attachment were uploaded into the issue through the Attachments section as described in our article: Add an attachment
- Upload an attachment using the "Attachment" feature:

- You can also upload the attachment into a comment
- Clone the issue and do not select the "Attachment" checkbox
- The new cloned issue will not include any attachments
Expected Results
The Clone feature will not clone attachments even if the attachment was uploaded into a customField
Actual Results
The Clone feature is cloning attachments because it is copying all customFieldValues from the origin issue.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
The only option will be to remove the issue from the custom field -> then re-upload the issue using the "Attachment feature" as described in the article: Add an attachment
- is related to
-
JRACLOUD-85201 Cloning Issues with attachments disabled will still copy an attachment file
- Gathering Interest