Jira Cloud automation: is this possible?

[Stefannie Tan]

If an issue on Project A with a related story ticket on Project B gets updated, is it possible to leave a comment on the Project B related story ticket (linked issues) with the details of what was updated?

thanks!

[Johan Markström]

Hi @Stefannie Tan! 

It's possible to do, what's your use case? 

[Stefannie Tan]

hi @Johan Markström , thanks for your response!

since we are using vendors, and they are using a separate board, they create a story ticket and link that to our original parent ticket.

but there is a worry that the parent ticket might be updated and they won't be notified. of course, we can use the Watchers option, but it might be better to leave a comment on the related tickets for all to see instead of relying on specific people to inform the rest (also less email notifications to the other team who also have other ongoing projects).

anyway, i found a similar past question! https://community.atlassian.com/t5/Jira-Cloud-Admins-discussions/Linked-Issue-resolved-leave-comment-on-linked-issues-Automation/td-p/1838524

however, i wonder whether it is possible to customize the comment to show exactly what was changed?

[Stefannie Tan]

to be more specific, I want to be able to print out the details of the changes in the following fields:

- description

- when an attachment is created/deleted.

[Johan Markström]

All right, great clearification.

Yes it's possible to comment something like: Description field for <issueKey> changed from <old value> to <new value>. Not sure how this works with attachments though, you'd probably print the file names for old value and new value.

When creating your automation rule, the changed values are stored in certain smart values :

{{fieldChange.fromString}} will return the old value in string format

{{fieldChange.toString}} will return the new value in string format. 

The example comment from above would look like this. 

"Description field for {{triggerIssue.key}} changed from {{fieldChange.fromString}} to {{fieldChange.toString}}"

Also, try and limit what issues should be commented on after the linked issue is edited. Since a ticket could be linked to multiple other tickets, define what sort of link (you could make a custom "vendor link" for this purpose) should trigger the comment action.