Here’s a sort of workaround. In Atlassian settings > Emails, configure your email domain and the email addresses you want to use (e.g. support@mydomain.com.)
In your JSM project settings, go to notifications, and set it to send notifications from that email address.
Emails now go out from "Project name" <support@mydomain.com> - BUT - the reply-to: header is hardcoded as <projectkey@myinstance.atlassian.net> - with no way to change or remove it.
In your project settings, go to email requests, and link a real (gmail, in my case) account of the same name - support@domain.com - to the project. JSM picks up messages from that mailbox, processes them, and responds with headers in this format:
from: MyCompany Support <support@mydomain.com>
reply-to: "support@mydomain.com" <support@mydomain.com>
The reply-to is a) unnecessary and b) ugly, using the email address in the realname field, but at least it works!
Caveat - this only seems to work if you let Jira collect email from the linked gmail inbox. Using gsuite advanced mail routing to forward emails to the atlassian project email address puts the atlassian address in the reply-to
NB I was worried this would send out a ton of emails and exceed my gmail sending limit, but in spite of giving Jira read and send permissions on the gmail account, it only reads the emails, and sends outbound through the Atlassian/AWS infrastructure.
Hopefully that helps someone!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.