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; } } }

Can we Clone an issue to a project in another Jira Instance and include attachments?

Matt Baker

Our company has two Jira instances. When we escalate from our support group JSM project in Instance A we would like to create/clone an issue into a development Jira project in Instance B.

I'm pretty sure I can take care of creating a 'clone' of the issue in Instance B using Jira automation and a webhook, but I'm stuck on how to include attachments. We almost always have log file attachments on the JSM issue that need to be included on the development issue as well. The developers only have access to Instance B. So just having them pull the attachments from the JSM issue in instance A isn't an option.

Accepted answers

Luka Hummel - codefortynine

Hi @Matt Baker

if you are willing to use an Atlassian Marketplace app, you can absolutely clone a JSM issue from between instances and include attachments automatically. That’s exactly what our app's Deep Clone for Jira Instance Clone feature is for.

How to set it up once

Have an admin in both instances go to Apps > Manage your apps > Instance Clone, click Add new target instance, and complete the short handshake. This connects A ↔ B securely.

How to escalate a single ticket with attachments

Open the support issue in Instance A and click Deep Clone (from the issue actions).
In the clone dialog:
- Under Target project, choose Clone to another instance…, pick Instance B, then select the destination Project and Issue type.
- In the clone configuration, tick Attachments (and anything else you need, e.g., Comments, Issue status, Work logs).
- (Optional) Keep Add issue link between clone and original on, so devs can jump back to the JSM ticket.
Click Clone immediately to create the issue in Instance B with all selected content.

Make it one-click next time

Save as preset in Deep Clone to reuse the same target/projects/fields.
Or automate it: add a Deep Clone Post Function on an “Escalate” transition, or trigger that transition from Jira Automation, so the clone (with attachments) happens as part of your escalation flow.

All comments

Tinker Fadoua

@Matt Baker

When you clone using automation I am sure you can add an action to include the attachments as well.

Can you please include the steps from your automation here? Please make sure to hide any confidential information.

Best,

Fadoua

Matteo Vecchiato

Hi @Matt Baker ,

Thank you for your question. Only with automation and between different sites, it isn't possible.

I suggest to have a look to this question: https://community.atlassian.com/forums/Jira-questions/Copy-attachments-using-automation/qaq-p/3103168#:~:text=Jira%20Cloud%20Automation%20cannot%20directly,on%20the%20source%20issue's%20transition.

Regards

Carlos Garcia Navarro

Hi @Matt Baker ,

I think you could export and import a CSV with the issues and their attachments from one instance to another. This other post has some ideas:

https://community.atlassian.com/forums/Jira-questions/Export-Import-attachments/qaq-p/1168399

and refers to this article to import the attachments referred in the CSV:

https://support.atlassian.com/atlassian-cloud/kb/jira-attachments-broken-after-importing-from-csv-file/

Trudy P Claspill

@Tinker Fadoua

The Clone action in Automation does include the ability to include attachments but it does not include the ability to select a different Jira instance or a project on a different Jira instance as the destination.

Tinker Fadoua

@Trudy P Claspill I never mentioned automation can work between 2 instances. I am curious to see what the reporter is trying.

All I said is cloning attachments cis available.

Best,

Fadoua

Clara Belin-Brosseau_Elevatic

Hi @Matt Baker

To implement your specific use case and escalate an issue with its attachments from one instance to another I can suggest trying our app Elements Copy & Sync.

It is designed to easily (and quickly) escalate issues between teams across projects and instances while cloning any work item field you like (attachment, comment, assignee, label...). You can even sync the two work items fields if needed.

Don't hesitate to have a look a the documentation and try the app (it's free for 30 days).

Luka Hummel - codefortynine

Hi @Matt Baker

How to set it up once

Have an admin in both instances go to Apps > Manage your apps > Instance Clone, click Add new target instance, and complete the short handshake. This connects A ↔ B securely.

How to escalate a single ticket with attachments

Open the support issue in Instance A and click Deep Clone (from the issue actions).
In the clone dialog:
- Under Target project, choose Clone to another instance…, pick Instance B, then select the destination Project and Issue type.
- In the clone configuration, tick Attachments (and anything else you need, e.g., Comments, Issue status, Work logs).
- (Optional) Keep Add issue link between clone and original on, so devs can jump back to the JSM ticket.
Click Clone immediately to create the issue in Instance B with all selected content.

Make it one-click next time

Save as preset in Deep Clone to reuse the same target/projects/fields.
Or automate it: add a Deep Clone Post Function on an “Escalate” transition, or trigger that transition from Jira Automation, so the clone (with attachments) happens as part of your escalation flow.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud