Synchronizing Attachments Between Linked Jira Issues Across Different Projects
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Summary
In certain scenarios, it may be necessary to synchronize attachments between linked issues from different projects within Jira. Although the 'Field value changed' trigger for the Attachment field can be utilized in Jira Software projects, it does not work with Jira Service Management Projects. This article outlines a workaround for syncing attachments between a Jira Software project and a Jira Service Management project, assuming that the issues in both projects are already linked.
Solution
Scenario 1: Copying Attachments from Jira Software to Jira Service Management Projects
To sync attachments when they are added to a Jira Software project and need to be copied to a linked issue in a Jira Service Management project, follow these steps:
1. Create an Automation Rule with the Trigger 'Field value changed' for the Attachment field.
Implementing this doesn't mean that attachments will preview fine. There is a chance they might encounter and preview not loading fine error:
- AUTO-723 - Cloned comments using Automation show attachments as "Failed to load".
The automation rules outlined above provide a foundational setup for synchronizing attachments between linked issues across different Jira projects. However, users are encouraged to include additional checks or actions to tailor the automation to their specific needs and project requirements. This may include specifying additional file types, implementing conditions for specific issue types, or incorporating other project-specific actions.
By utilizing these automation strategies, we can streamline the process of attachment synchronization, ensuring that relevant files are readily accessible across linked issues in different Jira environments.