How to create an attachment automation rule with a JSON file in a data center?

serkan_sezer

Hi, community, I wrote an automation to create a request from a PD project to a LP project. During the initial creation, all fields and attachments flow from PD to LP successfully.

I did this using an automation rule.

However, let's say a customer adds a new attachment during the process. I only want each newly added attachment to flow to the request linked via the issue link.

When I use trigger issue, all attachments flow back to the LP project. When I try to create a JSON file like "{{triggerIssue.attachment.last.id}}", the audit log shows success, but the attachments aren't reflected in the project.

How can I solve this?

Thank you.

Bill Sheboy

Hi @serkan_sezer 

First thing, I am using Jira Cloud and not Data Center.  Thus my suggestions are based on what I know about rules from that perspective.  With that out of the way...

For Data Center, have you checked the edit metadata to learn if attachments support an update operation with an ID only for the edit issue endpoint?

When I try this same scenario with Jira Cloud, I observe:

• adding an attachment requires sending the actual encoded attachment data, not an ID, and there is no rule action to do that
• using the "add" operation with an ID errors and recommends using a "copy" operation, however...
• using the "copy" operation is not supported with the endpoint the Edit Issue action uses
• and...when I tried directly calling the endpoint with Send Web Request to use the "copy" operation for an issue edit, it does not recognize the field, attribute, or operation

 

Kind regards,
Bill