nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cloning with Attachment

Justin Goodemoot

Hello!

I've set up automation to clone and include an attachment from the original ticket. The attachment gets included on the admin/team member view -- however, on the portal view, it is not included and not visible for admins or customers.

Is there a way to make the attachment on a cloned issue appear in the portal view?

I've added screenshots below of the cloning automation and the portal view of the cloned ticket, showing no attachments.

Screenshot 2026-03-18 at 6.05.10 PM.png

Thank you!

Accepted answers

Himanshu Tiwary_go407r

Hi @Justin Goodemoot ,

When an attachment is added from the issue view including by automation during a clone it is usually treated as an internal Jira attachment, so it shows for agents in the ticket but does not automatically appear in the customer portal. For portal customers to see it, the attachment typically needs to be shared in a public comment / reply to customer.Check this

Basically there isn’t a setting that makes cloned attachments automatically appear in the portal just because they were copied over. The usual workaround is to add an automation step after the clone that posts a public comment and includes the attachment, so the customer can access it from the request view.
Also Doc for referance

All comments

Himanshu Tiwary_go407r

Hi @Justin Goodemoot ,

Marc -Devoteam-

Hi @Justin Goodemoot

@Himanshu Tiwary is right here, this is also related that cloning is an internal job and it prevents that any attachment added to an issue would be customer available.

This could lead to security or privacy issues.

Gunjan Kumar_xl3r1p

Hi @Justin Goodemoot

From what I understand, this is expected behavior in JSM. When an issue is cloned, the attachment may be copied to the new Jira issue, but that does not automatically make it visible in the customer portal. For portal visibility, the attachment needs to be shared in a public, customer-visible comment on the cloned request.

So in this case, it does not seem like there is a setting to make cloned attachments appear automatically in the portal just through the clone action itself. The practical workaround would be to add another automation step after cloning that posts the attachment in a comment shared with the customer, so it becomes visible in the portal view.

Justin Goodemoot

Thank you @Himanshu Tiwary ! I have set up the automation noted in the article you shared and it appears to be working. Unfortunately, the attachment is still not visible on the portal, but I believe this is because the request type is blank and is not updating with the automation.

Justin Goodemoot

Thank you @Gunjan Kumar !

Justin Goodemoot

Thank you @Marc -Devoteam- !

Luka Hummel - codefortynine

Hi @Justin Goodemoot

If you want to avoid using the comment workaround or the potential flakiness of Jira Automations you can give our app Deep Clone for Jira a try.

Deep Clone will keep the attachment visibility when cloning between Jira Service Management spaces.

Additionally, you can use Deep Clone's Post Function Clone as a drop-in replacement for your automation.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management