How to move an attachment from one board to another using Automation?

[Soumyajit Pal]

A new ticket with same description including attachments should be created on another board. How to get this using Automation rule?

[John Funk]

Hi Soumyajit - Welcome to the Atlassian Community!

Just to clarify, attachments are not associated with boards and do not move between boards. Attachments are associated with Issues. Issues can show on one or many boards. 

So it sounds like you want to move either an attachment from one issue to a different issue? Or you want to have an issue with an attachment show on a different board? 

Which are you trying to do? 

[Soumyajit Pal]

Hi @John Funk  Thanks for your reply.

@Basically I want to move attachment from one issue to another. But they are on different projects. If the attachment is present then the same issue should be created with the attachment automatically

I want this using Automation.

[Marc - Devoteam]

Hi @Soumyajit Pal 

Welcome to the community.

Do you want a duplicate message with automation or do you want to show the original issue on another board.

Issues can be shown on multiple boards, as boards are based upon a filter

If you really need a duplicate issue, this can be done with automation, but:

When does this action need to take place:

• On creation of the original issue
• On a transition of the existing issue
• Manually triggered
• ...

Depending on when is useful on creating an automation rule

[Soumyajit Pal]

Hi @Marc - Devoteam 

I need duplicate issue, but if one issue has attachment then the duplicate should also get the same attachment,

I want this.

[Marc - Devoteam]

Hi @Soumyajit Pal 

I get this, but what should be the trigger to to run the automation?

So I can probably build you one, but when does it need to action.

- Creating an issue and check if attachment exits

- On adding attachment on an issue

- etc...

[Soumyajit Pal]

Yes,

Suppose, there is an existing "hh" issue on "x" project with an attachment, and now if that issue moved to done status in "x", then that "hh" issue should be created on "y" project including attachments.