/
@Mention handling

@Mention handling

Owned by Andy Brook [Plugin People]
Last updated: Apr 02, 2025
2 min read
@mentions in DC and Cloud are all internal to Jira and do not follow the IssueEvent pattern. As such, JEMH cannot intercept them, and we cannot customize them. Notifications come from the main Jira mail account as there is no way to do otherwise

JEMHC Notifications

We do in cloud what we do in DC, which is to detect the presence of an @mention in comments, and inhibit notifications for the party concerned to avoid duplicate content notifications. Jira itself will use its own internal outbound mail account to communicate mentions.

Atlassian do not provide a way to disable @mention notifications, see:

Mentions can be disabled for platform users via the user preferences.

Driving mentions via incoming mail

Its not straight forward right now:

MIME-Version: 1.0 Date: Sun, 19 Jun 2011 17:42:26 +1200 Subject: SUPPORT-14668 From: andy@test.com To: support@test.com Content-Type: text/plain; charset=UTF-8 Test with mention for jon doe [~accountid:1234123:abcdef-0123-45678-234ab-aabbccddeeff01]

Workaround

Use the related users emails in cc.

Identifying mail from JEMHC vs Atlassian Jira provided accounts

Identifying Atlassian Mail

X-Atlassian-Mail-Message-Id: <c354526a-5b68-455c-a2ed-a521eb332727@thepluginpeople.atlassian.net> X-Atlassian-Mail-Transaction-Id: c354526a-5b68-455c-a2ed-a521eb332727 References: <4iYaeuI9by5iYBIqlxZZAcDVhPFI5y7AkMvTnZr6L8E=@thepluginpeople.atlassian.net> Atl-Sent-Via: jira-np-distributor Precedence: bulk Reply-To: "[Plugin People] (thepluginpeople)" <support@thepluginpeople.atlassian.net> X-JIRA-FingerPrint: 2f2f114eb18de357b186c64ce2b5cbdee597c4e4885b26897340ed122e4cee0f Message-ID: <c354526a-5b68-455c-a2ed-a521eb332727@thepluginpeople.atlassian.net> From: "Andy Brook [Plugin People] (thepluginpeople)" <support@thepluginpeople.atlassian.net> In-Reply-To: <4iYaeuI9by5iYBIqlxZZAcDVhPFI5y7AkMvTnZr6L8E=@thepluginpeople.atlassian.net> Subject: [JIRA] Andy Brook [Plugin People] mentioned you on SUPPORT-14668 Feedback-ID: ip.5a17627f:pr.jira:la.jira/jira_issue_single_jnd:atl-mail-out

The above contains some giveaways that its from Atlassian, the “X-Atlassian-” headers for one. Line 9 has a support@thepluginpeople.atlassian.net value, the .atlassian.net domain is the bundled mailbox that each Jira instance gets. The ‘support’ part comes from the project specific setting, it will be a default value if not set:

image-20250402-142757.png

Identifying JEMHC Mail

JEMHC doesn't use .atlssian.net mailboxes, 3rd party use is not supported by Atlassian or us, mail sent by JEMHC will be from your JEMHC outbound mailbox, eg:

From: PPL-JEMHC-Support <jemhc-support@thepluginpeople.com> To: "Andy Brook [Plugin People]" <andy@thepluginpeople.com> Message-ID: <2091569681.32761.1743603318289@ip-10-0-3-85.ec2.internal> In-Reply-To: <JEMHCloud.prod.JEMHC-5056@thepluginpeople.atlassian.net> References: <JEMHCloud.prod.JEMHC-5056@thepluginpeople.atlassian.net> Subject: (JEMHC-5056) PreProc Script Task needs to expose the "mailboxAddress" from the message source MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_32759_1859046724.1743603318286" Precedence: bulk Thread-Index: PEpFTUhDbG91ZC5wcm9kLkpFTUhDLTUwNTZAdGhlcGx1Z2lucGVvcGxlLmF0bGFzc2lhbi5uZXQ+ X-JEMHC-FINGERPRINT: 1f80d26a18c90fa411db199196635f55 X-SentBy-JEMHC: true

Here, Line 1 indicates that the mail is from @thepluginpeople.com which is expected. Knowing this is a JEMHC mail can also be determined by lines 11 X-JEMHC-FINGERPRINT and X-SentBy-JEMHC

Related content