Images lost when scalating /cloning tickets

[Carlos Morell]

When I want to clone a ticket in Jira, the text remains the same.. but the images are shown as unavailable. Some explanation for this?

[Chitra Nagdeo]

Hey @Carlos Morell ,
Welcome to Atlassian community!

Please note when you clone a Jira issue, the default behavior is to copy the issue’s fields (summary, description, etc.), but attachments (including images) are not automatically cloned.

You may explore Clone issue option, the action component can create a new issue and copy across all field data possible, including the ability to copy attachments. Also while cloning a workitem please use the option Include Attachment and it must copy the attachment to the cloned workitem.

I hope this helps, have a good day ahead!

Regards
Chitra Nagdeo

[Clara Belin-Brosseau_Elements]

Hi @Carlos Morell

Welcome to the Atlassian Community! 

When you clone an issue in Jira, only the text data (summary, description, comments, etc.) is copied by default. Attachments and inline images in the description are not fully duplicated: the new issue’s description still references the original file paths, but those links become invalid once the clone doesn’t include the attachments themselves. That’s why the images show as unavailable.

If you want images and attachments to be properly copied and remain visible in the cloned issue, you’ll need a solution that can handle media files as part of the cloning process.

One option I can suggest is trying our app Elements Copy & Sync to:

- Clone issues with all attachments and inline images included

- Keeps field formatting and links intact

- Optionally synchronizes updates between the original and cloned issues

You can try it for free on your instance!