By default, $context.issue.fields.comment.comments contains all issue comments, regardless of comment visibility restrictions. This means, by default, custom templates relying on the $context.issue comments can show all comments to recipients that may otherwise not be able to view these comments.
If you do not want to expose all comments, you must use $jemhUtils.filterRestrictedComments($context.issue.fields.comment.comments) to remove comments the current recipient should not be able to view.
This script will gather and render all comments that the recipient has permission to view. e.g. Internal Comments are not rendered for Customers.
...
Previous Comments with a Reference to an attachment
| Info |
|---|
Please see https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/50724928/How+to+verify+comment+visibility+applies#Limitations-of-retrieving-restricted-visibility-comments for more information regarding historic comment references for Software projects. |
If the previous comments contain a reference to an attachment, then it could result in those attachments being sent multiple times, as JEMHC will attach all attachments that have been referenced within the email body. This will then result in your data usage being used more quickly as it will increase the email size.
...