Doing Jira Service Management Customer Notifications Right

Jira Service Management can be used to help many different types of customers in many different ways. For a customer service management project where your customers are external to your business, brand identity is an important aspect. For this, Jira cloud allows custom email addresses to be used for notifications. For example, you can use your own email domain for sending emails to your external customers. Today we are excited to announce that emails sent via custom email addresses can be formally signed to pass DMARC security checks, and ultimately ensuring your messages are delivered to their recipient.

What is DMARC/DKIM?

Domain-based Message Authentication, Reporting & Conformance (DMARC) is a protocol used to verify that emails are actually being sent by the person who owns the email domain. This protocol uses Domain Keys Identified Mail (DKIM) to prevent hackers from impersonating email domains.

Why is this important?

Although DMARC has been around for many years, it is only recently that mail servers have started to strictly enforce it. As a result, it is becoming more common that unsigned emails are flagged, moved to spam, or worse blocked completely.

How do I enable a custom email address for my JSM project?

Add your custom domain

Screen Shot 2021-12-02 at 2.55.20 pm.png

  1. Navigate to Atlassian Admin, by going to the top-right Settings (cog)  and selecting User management.
  2. From the top horizontal navigation choose Settings.
  3. Choose Emails from the left-side panel.
  4. Make sure you’re on the Email domains tab, choose Add domains.
  5. On the Add email domain window, enter your domain and select Next.

Screen Shot 2021-12-02 at 2.18.17 pm.png

Managing your DNS

For this step, you will need a Network Administrator who can apply DNS changes to your domain.

You will need to add each of these records to your domain's DNS. This will be slightly different based on your domain registrar

Screen Shot 2021-12-02 at 2.18.41 pm.png

  1. SPF - TXT - You might already have an SPF record for your domain. In that case, you must include this record with a space after v=spf1
  2. DKIM Active, DKIM Fallback, Bounce - CNAME - Depending on your domain registrar you might need to drop your domain from the name/host value e.g. atlassian-bounces.acme.org becomes atlassian-bounces.
  3. Verify - TXT - This lets us verify and associate your domain with your Atlassian Organisation.

Once all the changes have been made, your DNS will be verified and the domain status will change to Active.

Add your email addresses

Once you have a domain added, you can add email addresses that are allowed to be used for sending notifications.

  1. Go back to the Email addresses tab on the Settings > Emails page.
  2. Click Add email address.
  3. Select a domain and enter the prefix of the email address then select Add. You can add up to 10 email addresses at a time.
  4. Select the products for which the email addresses can be used for sending notifications.
  5. Click Add email addresses.

Screen Shot 2021-12-02 at 4.35.00 pm.png

Apply an email address to a project

Now that you have a list of allowed email addresses with your domain, you can apply an email address to a project for it to start sending email notifications using that email address.

  1. Go back to Jira Service Management (or any Jira cloud product) and select the project for which you want to change the email address for notifications.
  2. From the left-hand project sidebar, go to Project settings and select Notifications.
  3. Under the Notification email heading click Edit.
  4. You will see the projects email address for notifications, click Edit.
  5. In the drop-down select the custom email address you created for your custom domain.
  6. Click Save.

Your project will now send notifications from your custom email address.

Bonus Step

Have you considered adding a custom email address for inbound to match your custom email address for notifications? Learn more.

What if I am already using a custom email address / domain

Not a problem. Existing custom email addresses/domains will continue to function as they did previously. But it is recommended that you upgrade to the new method to take advantage of the correct DMARC/DKIM signing.

6 comments

David Brieck Jr
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 9, 2021

Thank you, though it's disappointing that it's taken over 3 years for this feature from when it was first officially requested. 

Like # people like this
Mike Tyler
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 15, 2021

How do I adjust the name?  Email is being sent from the correct email but showing as Automation for Jira.  This is not what I want customers to see.  Where can I adjust the email name to show correctly?

Kevin Pfaffhauser December 30, 2021

@Mike Tyler this you can do under System > General Configuration > Email from 

Another issue though is that there seems to be no way to route our custom notification email address to the respective issue upon a reply?

It should trigger a comment with the respective issue when replying to the email. How can we accomplish this?

We've tried forwarding to jira@SUBDOMAIN.atlassian.net to no avail.

Kristin Lyons
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 30, 2021

I know a handful of people who are going to love this

Benjamin Paton
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 3, 2022

@Kevin Pfaffhauser ideally you would have a unique email address for each project. Then connect it to the project both for notifications and in Project settings > Email requests.

This will ensure replies are captured.

Paul L Fisher
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 21, 2023

It no longer shows the SPF record.

Like # people like this

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events