-
Sub-task
-
Resolution: Fixed
-
None
-
None
-
None
Jira Service Desk next gen does not allow you to set an outbound email like the Classic JSD did, eg JSD next-gen supports e-mail delivery only from jira@<yourdomain>.atlassian.net .
You would still be able to receive tickets in the system through your custom e-mail address but customers would receive ticket information with the jira@<yourdomain>.atlassian.net signature.
The below screen does not exist in JSD next-gen
- mentioned in
-
Page Failed to load
[JSDCLOUD-8346] Outgoing email address configuration
FYI: I followed below guide to solve the same issue and it works fine.
Don't forget to look at the bottom part as well...
Why don't use domainkey like Statuspage ?
Rather than force customer to use a subdomain, statuspage just test spg1._domainkey & spg2._domainkey
https://support.atlassian.com/statuspage/docs/set-up-spf-and-dkim-signatures/
It's odd to use s1 & s2 who are already used by a lot of customers
@John Parker - I followed this instruction https://confluence.atlassian.com/adminjiracloud/configuring-jira-cloud-to-send-emails-on-behalf-of-your-domain-979428371.html
After implementing it I struggled to find where the send out should be configured but following @Damian Finger hint it worked out perfectly fine. Hope this helps.
@maris svilans - I am experiencing the same issue as Damian. As soon as I change the notification email to anything other than jira@ourdomain.atlassian.net email stops functioning entirely.
When I first installed my Next-Gen project I opened a ticket with Jira about this, and their official response was that customized outgoing email is not supported in Next-Gen projects, I have not seen anything from Jira that changes that stance. It makes no sense, it is not documented, and is something that most enterprises would consider essential. Jira's response is to shrug their shoulders. I'm happy to hear that it is working for you - I'm not sure how, but that's nice. The rest of us are left hanging though.
Indeed, instruction missed that setting should be done for individual project, as Damian mentioned under Next Gen projects (I had service desk project) >Projects Settings > Notifications> Notification Email it is possible to create custom email. All is working and custom email is sent on behalf of company Domain. All is working and customers receiving emails from Services Desk Next Gen project.
I believe in Next-Gen; under "Project Settings" > Notifications > Notification Email
Is the setting we are all looking for. However, I have this setup, and am not receiving emails at all from the Service Desk.
I just spent three days building out a Next-Gen project only to discover that this feature is missing. I now have to start over again with a basic project at my own time and expense. Please at the very least update your documentation Configuring Jira Cloud to send emails on behalf of your domain [https://confluence.atlassian.com/adminjiracloud/configuring-jira-cloud-to-send-emails-on-behalf-of-your-domain-979428371.html] to reflect this lack of functionality.
Please.
It would have saved me hours of work because I used this to set it up and nowhere in the page does it explain it does not work in your Next-Gen projects. I hope that adding it might save others from the same.
And, Lukas is exactly right, "I don't think Atlassian should be pushing new users to use next-gen if such basic functionality is missing."
Please find the instructions on how to configure notification email here https://support.atlassian.com/jira-cloud-administration/docs/configure-jira-cloud-to-send-emails-on-behalf-of-your-domain/