I’m stuck on a Jira setup problem. We’re trying to get Jira Software and Jira Service Management to work together smoothly. Our company doesn’t have many JSM licenses, so we’re limited to using Automation for this task.
So far, I’ve managed to sync comments (both public and private), statuses, fields, and even reporters. But I’m hitting a wall with attachments. Every time I try, they end up being duplicated.
Does anyone know a good way to sync attachments using just Automation? We’re on the Data Center version, not cloud.
I’d really appreciate any tips or tricks you can share. Thanks in advance for your help!
hey Noah, i feel ya on the attachment sync problem. it’s a real pain! have you tried using a custom field to track attachment IDs? might help avoid duplication. another idea: maybe set up a webhook to handle attachments separately? just brainstormin here. good luck with your setup!
As someone who’s worked extensively with Jira Data Center, I can relate to your attachment sync dilemma. One workaround we implemented was using a shared network drive accessible by both Jira Software and Service Management. We then created an automation rule to save attachments to this shared location and update a custom field with the file path. This way, both systems could access the same files without duplication.
Another trick we found useful was leveraging the ‘Issue Link’ feature. By creating a custom issue link type between Software and SM issues, we could then use automation to copy the attachment links rather than the files themselves. This approach saved storage space and prevented duplication, though it required users to click through to view attachments.
These solutions aren’t perfect, but they helped us manage until we could upgrade our licensing. Hope this gives you some ideas to explore!
I’ve encountered similar challenges with Jira integration. One approach that worked for us was implementing a custom script using the Jira REST API. This allowed us to selectively sync attachments based on specific criteria, avoiding duplication. It requires some coding knowledge, but it’s quite flexible. Another consideration is using a third-party app from the Atlassian Marketplace that specializes in cross-project synchronization. These often handle attachments more gracefully than native automation. Just be mindful of potential performance impacts on your Data Center instance, especially if you’re dealing with large attachments or high volume.