In the Notification Scheme for my projects, I always set the "email" field to "email@example.com". When one user makes an edit, etc, to an issue that causes a notification to be sent, the email is listed as from "Joe User (JIRA) <firstname.lastname@example.org>".
Then, other users who get the email want to reply to Joe, so they just hit Reply in their email client, but their reply goes to email@example.com.
Is there a way to configure JIRA to send emails "from" the person who made the updates/edits/etc?
There's no way to do this natively in JIRA. The JIRA Notification scheme can be configured to use a certain email address for ending email addresses and it does not have an option to "use the reporter's email address" and I agree with it. It's a system generated email so it should come from a system email.
If you want to purse this option, take a look at the JIRA ScripRunner add-on Send Custom Email. You can manually set "FROM:" value for each workflow -create event (if you are willing to go that far).
Email this issue supports this in multiple ways out of the box, including sending customizable emails manually or upon events, transitions
To configure From address for emails sent upon events, you must configure:
Thanks. I can get JETI to send emails when I'm adding a Comment, but not when the issue is Updated. Seems like I don't understand how to setup the Notifications/Contexts to allow different events within the same project to use different templates. I sent you a direct email, so we can work it out. I'll update this page with the results, so others can see it later too.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs