Problem Definition

When a user is @mentioned in a comment on a Jira Cloud issue, the notification email contains only a subject line ("[User] mentioned you on [ISSUE-KEY]") and action links (View Comment / Add Comment). The comment body text is not included.

This forces recipients to leave their inbox and navigate to Jira just to read the comment and determine whether action is required. For teams that rely on email as their primary triage mechanism, this creates a broken workflow — every single mention requires a context switch regardless of whether the comment is urgent, informational, or irrelevant to them.

The inconsistency is notable: the "Issue Commented" notification (sent to watchers/assignees/reporters) does include the full comment body in the email. The @mention notification is the only type that omits it, despite being the most targeted and action-oriented notification a user can receive.

Suggested Solution

Include the comment body text (or a reasonable preview) in the @mention notification email body, consistent with how the "Issue Commented" notification already renders comment content for other recipients.

Render comment body below the existing "X mentioned you on ISSUE-KEY" header

Maintain existing "View Comment" / "Add Comment" action links

Respect existing comment visibility restrictions (e.g., restricted comments should not be exposed to users without access)

Workaround

The "Issue Commented" notification event does include the full comment body in the email. Users who are added as Watchers on an issue (or are otherwise recipients of the "Issue Commented" event via the project's Notification Scheme) will receive comment content in their inbox, including comments where they are @mentioned.

Admins can configure who receives the "Issue Commented" notification via Jira Administration → Issues → Notification Schemes, adding recipients by project role, group, or watchers.
Users can also manually Watch specific issues, or an automation rule can auto-add watchers based on criteria (assignee, reporter, etc.).

Limitation: Watchers receive notifications for all comments on the issue, not only those where they are @mentioned. This increases noise and is not a 1:1 replacement for targeted mention behavior.