Jira Misc Workflow Extensions email issue post function - What is the reply to?

[Mike Rathwell]

I've been trying to use the JMWE email issue post function. The idea is that should one reply to the email that comes out of that, it would go back into JIRA and comment the issue it came from. However, it appears that the "reply to" is set at the user that did the transition (or what is set in the hard code field).

The email client sees and displays the executing user's name with an email address of my Jira environment. HOWEVER, whenever I try to reply to it, it opens the reply with the email address of the user (as stored in the Jira user base).

Is there any way to override this to have it send FROM jira vs. the user that initiated?

[Mike Rathwell · Accepted solution]

I solved it myself.... it's a BIT of a hack but I created a service account in Jira with the correct name and email address but doesn't have log in privileges. Allows it to be used as the reply to but doesn't take up a license.

[Mike Rathwell]

Seems a recent update of JMWE allows one to spec the system email address as the sender... I've coded around it (and actually turned out to be a better solution) but resolved now.

[Payne]

Another option is if you also have ScriptRunner installed, it also offers an email post function, and in its configuration section you have complete control over to, from, reply-to, cc, and bcc addresses (you basically have an instance of an Email object [https://docs.atlassian.com/atlassian-mail/1.3.23/com/atlassian/mail/Email.html] to do with as you please).

-Payne

[Mike Rathwell]

Thanks @Payne. I did look at that and keeping it in my back pocket if I can't work out the rabbit hole I am down right now.

[David Fischer]

Unfortunately, Jira decides on its own what the Sender information should be - the Ad Hoc Notification API just allows to specify the user that should be considered as the sender, not the reply-to address.

[Mike Rathwell]

Thanks @David Fischer

As mentioned I found a work around but I am also going down another direction by putting an html tag in there with the response I am after (actually solves a few problems by doing that)

What I am doing is having users NOT in JIRA be able to transition an issue via email (keywords with Automation transitioning when it sees them). The "instructional" email coming from a PF. I'm now creating the html tag to create the email automatically with correct reply-to, subject line, and key words in the body. Serves to drool-proof it a bit more.