Automation for Jira Cloud - clone issues and copy attachments

[Samuel Bar]

I have created a rule that clone Bugs from one Project to another one.
I can update files during the clone step(see attached image), the only thing that can not find how to do is to copy the attachments from the original Bug to the clone one.
Any suggestions are welcome

[wwalser · Accepted solution]

Automation doesn't currently support manipulating attachments in Jira Cloud. Unfortunately Jira Cloud doesn't have APIs around the management of attachments so we're not able to implement this just yet.

There is an open issue tracking the implementation of this feature here: https://codebarrel.atlassian.net/browse/AUT-1030

[badi]

We really need this feature!

[zafar kamal]

yes agreed , we really need this feature , how soon can we get this feature rolled out 

[Chris Evans]

We need it too! 

[Mickael Belloulou]

We need it too! 

[Limber]

I join the request. Some update?

[Gidi Geras]

This really creates problems in our flow.

Any ETA for this?

[Sean Cuevas]

Hi There,

Missing this functionality from the Server version of this app. Any update?

[Nick Read]

+1

[Dimitar Trendafilov]

Is it possible to have somehow JIRA show the linked attachment from the original issue?

[Srujan kumar]

+1

Missing this feature from cloud version.

[Shannon Balser]

+ 1 

Any updates here?

[Marlene Kegel - codefortynine]

You can also automate cloning of issues including attachments with our Jira cloud app Deep Clone for Jira.

It is possible to create a Deep Clone post-function that clones on transition. Cloning attachments is also possible of course.

If you don't want to change the issue status to trigger a clone, you can integrate Deep Clone with Jira Automation using looping-transitions.

If you need more functionality don't hesitate to get in touch with our support. We're always open to implement new features.