So say i have two issues. We link them together with the edit -> linked issues. So now they are linked. However when i change /comment / modify one of the issues, all request participants on both issues are not notified. Only on the issue that i change / modified / commented on.
Is this how it is designed to work? What the heck is the point of linking then? its just a visual thing, no cascading of notifications, or grouping of agents or request participants?
It seemed like such a promising feature. people put in duplicate work orders and you can group them together and solve them all at the same time. But if it doesnt send an email to all, then i have to manually merge them and the promising idea is reduced to a only slightly useful one. Is that the intent of this field? i did read the linking issues part of the manual but notifications are not mentioned.
Hi @JiraYo,
Notifications in Jira are event-based. The set of events is quite extensive triggering notifications is very extensive, as you can read in this section of Atlassian documentation on notification schemes.
As you may find from that read, notifications are triggered from either events on an issue or from workflow related events. Your observation that notifications are not propagated to linked issues is correct.
In order to trigger notifications on linked issues, it is a matter of triggering the same events on your linked issues as well. As you labelled your question with Jira Service Desk, automation rules might come in handy to cover workflow related use cases, e.g. when you want to update the status of one ticket based on a transition of a linked issue. As long as you trigger the right events on your linked issues, notifications will go out for them as well.
Regarding updates, comments and attachments, there's definitely some interesting apps in the Atlassian Marketplace that can help out in that area too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.