I have created a rule in Jira automation to sync the comments in the linked Jira tickets. That means if I commented on Jira issue 1, that same comment should be reflected in Jira issue 2 (Jira issue 1 and Jira issue 2 are linked to each other) and vice versa. It is working for regular comments but not for attachments. If I am attaching a file in the comment section of one issue, it is not showing properly in the other one, and shows an error as "failed to load" or "Preview unavailable" . I am on Jira Cloud Premium.
Hi @Amit Jash , to copy attachments from one issue to another you should use the edit issue action and choose the attachment field and you can select a copy from option. In other words, the attachments will not come over with the comments as you have found. They need to be done separately. You should be able to do this within the same rule or you may choose to do it in a separate rule.
Thanks, @Jack Brickey That works for Jira software issues as we have an option to attach files. But how about JSM tickets(in the agent queue) as I don't see any other option to attach files apart from the comment section. Do we have any similar attach options in JSM similar to Jira software?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Amit Jash - I am running into the same issue and even creating an additional rules to update the linked tickets with the attachments isn't working for me. Did you find a resolution to this?
This is the additional automation I created that isn't working:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Amit Jash Does it also work if additional attachments are added after the ticket has already been created?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@James Carnes-Dela Cruz for that you have to create a separate automation using When: Issue updated Trigger
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.