Hi @Koyel Guha,
The issue you’re facing with duplicate attachments syncing to Jira while comments update correctly is a common challenge in integrations involving attachments.
Here are some things to consider and check:
- Attachment Identification: Make sure your integration logic checks whether an attachment already exists in Jira before adding it again. Without this check, every sync cycle may upload the same file repeatedly.
- Timestamps or Versioning: Use metadata like attachment timestamps or unique IDs to identify the latest attachment and avoid duplicates.
- Lookup Logic for Attachments: Similar to how you’re handling comments with “lookup latest,” apply a similar approach to attachments so only the newest version gets synced or updated.
- Cleanup or Deduplication Steps: Some integration tools offer settings or workflows to clean up duplicates or prevent re-uploading files.
If your current integration setup doesn’t support these checks well, using a platform designed for advanced sync logic can help. For example, OpsHub, an enterprise –grade integration solution and a ServiceNow Partner can handle attachment syncing with proper deduplication and update logic, reducing duplicate data and keeping systems aligned. Bidirectional deep data sync, all this without writing a single line of code 🙂
Hope this helps! Let me know if you want guidance on implementing these checks or more details on integration options.
