Copy attachments using automation

[Yogesh Mude]

We have two different jira cloud sites and one particuler workflow transition we are triggering the automation rule and it will create a jira work item in the target instance but also we want to copy the attachments from source work item (one site) to the target work item (another site).

Does anybody configured this using the jira cloud automation rule? if so, may i ask you how?

Note: I am not using any third party vendor app.

Thank you.

[Clara Belin-Brosseau_Elements]

Hi @Yogesh Mude

As Utkarsh mentioned previously, Jira’s native automation doesn’t currently support copying attachments directly from one issue to another.

I can only suggest trying our app Elements Copy & Sync to facilitate the copy of attachments from one instance to another.

It's a simple, no-code solution, don't hesitate to give it a try.

[Luka Hummel - codefortynine]

Hi @Yogesh Mude

In Jira Cloud, automation rules unfortunately can’t transfer attachments between two different sites. That’s why your rule is able to create the issue in the target instance, but not move attachments over.

If copying attachments is a key part of your workflow, and you are willing to use a marketplace app, our app Deep Clone for Jira can help. With Deep Clone, you can:

• Clone attachments along with issues, comments, work logs, subtasks, and more between projects or even across Jira Cloud instances using the Instance Clone feature.

• Trigger clones manually, in bulk, or via workflow post functions so you can automate the process when a transition happens.

That means instead of only creating a shell issue via automation, you can fully replicate the source issue in the other site, including its attachments, and keep the two in sync if needed.

[Utkarsh Agarwal]

Hi @Yogesh Mude 

Jira Cloud Automation cannot directly copy attachments across two Jira Cloud sites. You can create the issue in the target site via Automation, but attachments require a workaround.

The usual method is:

1. Automation triggers on the source issue’s transition.
2. Create the target issue in the second site.
3. Use REST API to fetch attachments from the source issue.
4. Upload them to the target issue via REST API (POST /rest/api/3/issue/{issueId}/attachments).

⚠️ Limitations:

• Automation alone can’t reliably handle attachment bytes.
• You’ll need a small script or webhook-based function.
• Watch out for authentication, file types, sizes, and API rate limits.

Anyone figured out a way to do this fully within Automation without scripts? Curious to know!

[Yogesh Mude]

@Utkarsh Agarwal thank you for the response. these steps are already been followed by me and trying to find out the solutions. even, i am also eger to know. 😊