I was thinking this option would not be greyed out anymore after adding a custom email address. Imagine my surprise when it didn't and I find this article instead

We need this feature Atlassian.

Please implement this.

Our regular Jira notifications are already being sent by a custom domain. We can also process incoming replies to that address.

Processing replies to an email sent by an automation rules is impossible because of this restriction.

We also want our email to be more professional and trustworthy by using our own domain.

+1

24e3f7482be1 get a clue mate, using a paid plugin is not a solution. That's all there is to it.

Hello,
This is just my annual check in to remind you to

DO SOMETHING ABOUT THIS REQUEST

Thank you

Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?

Hi all, to better track customer demand for these features, we’ve split this into the relevant asks:

• Email Domain Customization - Changing "From" Email Address in Automation and “Reply-To” Email Address in Automation - https://jira.atlassian.com/browse/AUTO-76
• Support for emailing over 50 users in automation (currently prevented by the role user limit) - https://jira.atlassian.com/browse/AUTO-127
• Ability to send attachments via Send Email action - https://jira.atlassian.com/browse/AUTO-1130
• Support for email templates - https://jira.atlassian.com/browse/AUTO-216
• More options for the “to” field - https://jira.atlassian.com/browse/AUTO-1568

We have a client that would benefit greatly from automated email reminders coming from an address their clients would recognize. They are blocked until they can customize the from: address. 

Yes you can! To control the email address of the outbound jira automation email you can use a workflow transition strategy along with the "Email this Issue for Jira Cloud" plugin.

In the plugin 1st configure an outbound mail connection. You can get your email admin (O365 or other) to create separate mailboxes for each project if you want to both send and receive traffic related to comments, status changes, and automations uniquely for each project.

Then modify each of the workflows involved to have a new transition called "send email". You could optionally allow the transition to be used by all statuses, and of course you could just do a send email transition to a new status in the workflow called for example "EMAIL SENT" and add a "return from EMAIL SENT" transition back to the status it came from. (tip: https://confluence.atlassian.com/jirakb/how-to-transition-to-the-previous-status-of-an-issue-using-automation-rules-in-jira-1236599919.html)

Configure the workflow transition to send email via the post function "Send Customizable Emails - Email This Issue Workflow Post-function sends a customizable email to various recipients you can configure"

In the "Email This Issue" "Outgoing Emails" / "Advanced Email Configuration" "Add" and new configuration for each project, be sure to select the scope (the project) and on the last page of the configuration tool, you can select the various email boxes that you setup....for example if you had your email admin create a mailbox for each project.

Now all you have to do is setup your email content templates, then create a notification scheme for each project.

Now when your automations "transition the issue to EMAIL SENT" the workflow post function will send an email with the email address you want (i.e. one of your company email box addresses) and either the manual content you enter on that post function or it will use the template (I like the template better because it is prettier) depending on your selection/preference.

If you configure your template subject field properly, many of your templates can be used across all projects. ($!issue.key) $!issue.summary#if("$!mailSubject" != "") $!mailSubject#end

Same goes for the body is you use mostly system fields:
---------------------------------
Issue internal comment.

$!currentUser.displayName has just commented on this issue.

$!issue.project.name / $!issue.key <<<Agent Link
#renderLinkToPortalRequest($linkText) <<<Customer PORTAL LINK !!!

$!issue.summary
#renderChanges()
INTERNAL AGENT COMMENT:
#renderIssueComments("desc" "1" "")

Template = Issue Commented Agent Internal - OK
---------------------------------

That is all there is to it.

We have been working on deploying Jira for a few months now but we have hit a major barrier with not being able to send emails the way we would expect. Our customers communicate with us primarily by email and without a tailored way to email them back, we are unable to proceed. Any information about when these features will be released would be greatly appreciated.

We especially need to be able to change the 'send from' email from automations so that it is coming from the Service Project email address.

Perhaps you should split this one-big feature into smaller parts (like according to the paragraphs of the description) and already start some action...? It's MUCH better to have 1 small feature already implemented that whole package still in "Gathering Interest"... 

I think that limiting group email sending to 50 people is too small. There should be 500 people!

This would be such a big feature addition.  I'm surprised it's not already done.

This will solve any need to add complexity with apps/additional mail handlers. 

+1

Amen Charles....we would really, really, like for our automation rule emails to come from our company's domain instead of atlassian's.

Yes it is for us a big issue. We send onboarding email thru Jira Automation and it is being more and more rejected by mail servers vs when we send thru our email domain. We configured Email Domain verification in Atlassian and use specific email from our domain and it being more accepted / view vs being blacklisted / discarded.  A must asap please.

Definitely would like to have the option to change FROM address. With scams being common these days, customers are wary of email address domains, having the .attlassian.net makes it look like a phising or scam email , which will either get ignored or filtered by customers

Jira automation is amazing, but for us, its biggest flaw is that we can't change the sender address.

There is no sense why we can't change the address of the notification mails, but not for the "send mail" action in the automation rule. This need a fix asap.

Please add this functinoality to allow us to change the "from" email address sent out of Jira automation. Being able to set a common email address will mean that they are read. With a generic, spam looking email address, we will undo the benefit of automating so many things as they will be ignored or filtered. 

Merry Christmas to everyone and I wish us all that Atlassian has many New Year's resolutions - e.g. to solve this issue!

The ability to send notifications from a verified (by DNS entry) managed e-mail domain has been available for a while. It's so frustrating that functionality like this isn't applied to all parts of the system.

I know that Automation started as a separate addon 'Automation For Jira' but by now Automation is a neccessity and an integral part of Jira.

Also, if you're going to close other FRs as duplicates and combine them into one (AUTO-373 119 votes), at least pull in the vote count from the duplicate tickets so that you have a true reflection of the demand.

Otherwise it appears like Atlassian is rigging demand so that they don't have to implement customer requested features.

Currently I have to butcher together Power Automate and Jira to send the emails that would be so easy if we could change the FROM address for emails. 
Please introduce this feature. It's insane to me that this still hasn't been done.

Please add the option to change the FROM email address. Currently, the "Send Email" automation can't be used for external customers because the FROM email address is fixed on @subdomain.atlassian.net

Please add the option to change the FROM email address. Currently, the "Send Email" automation can't be used for external customers because the FROM email address is fixed on @subdomain.atlassian.net

Please focus on this ticket, it need to be solved. We need to send automation mails from our current domain. It does not look good if you use "External" remarker as default and a quite internal mail from Jira looks like coming from the outsinde.

Adding my support for these fixes, especially the sender address change, but so many of these fixes should be quite simple and could revolutionise this whole feature.

We need the ability to send ALL and I mean ALL Jira related emails from our own tea.texas.gov domain.  We simply cannot support sending our government employees emails regarding the internal workings of the agency when the source of those emails is an external commercial domain.  That is especially true for the sensitive nature of what we do.  

I see this Jira cloud related issue has been open for almost 3 years.  It is way past time to get this fixed.  I vote for emergency escalation of this issue.

+1 on this. The inability to change the "from address" needs fixing. This has made updating and engaging our customers (in terms of support) more challenging!

To send automated custom emails from Confluence Cloud and to address several of the points mentioned in this thread, check out the custom notifications feature in the Better Content Archiving app.

Features:

• You can set up a flexible schedule using a CRON expression.
• You can enter a CQL query to collect the pages and blog posts for the notification.
• You can customize the email subject and the email body (HTML) by editing a reusable email template.
• You can select any combination of the following recipients: last modifier, author, content owner(s), space administrator(s), specific user(s) and specific group(s)
• These settings are wrapped by a notification scheme that you can use in any space, therefore it is very manageable even in large Confluence sites.
• Available for all Confluence plans (incl. Free and Standard, too) and free up to the 10 users.

The Send Notification action of the Automation should allow selecting Custom Email Addresses that have been configured for the Cloud account, so we can match sender for emails sent from rules which replace Customer Notifiications (because no logic can be applied to the sending of Customer Notifications).

This e-mail address has been in place for years, so the change ended up impacting some of our notifications from rules we've created through Outlook or text messaging.  From the service side resulted in delayed responses from the business.  It would be a nice feature to have a way to designate the from e-mail ensuring, that future updates do not impact existing processes.

@Nerea, thanks for the reply.

My issue is - my personal Gmail sent my automated message straight into SPAM folder even though the SPF, DMARC and DKIM tests were all PASSED.

EDIT: It happened today, with the new email used.

From where I stand, the issue is not resolved. I want to send my automated messages from support@herocoders.com, which is configured to send notifications to customers already...

Update: my problem is not quite related to this issue after all. Actually we are not sending an email, only posting a comment on a Service Management issue, visible to the user, which triggers an email. However the comment author appears as Automation. We can change automation to a specific actor, but what I need is a "smart value" assignee, instead of a specific user.

There are many possible improvement captured in this one issue...

The only one I need wish to have is setting the from address (AUTO-373) in the context of Jira Service Management. I wish the emails sent from Automation are using the same from address as the one sent directly from the Service Management project.

@Wojciech Wardaszko s[HeroCoders] you are right, It is not exactly the feature that was requested, sorry for yelling "victory" that fast , for us, being able to not go to spam makes the difference between using or not automation for custom email notifications. I hope Atlassian will implement the original request soon, It is a lot nicer to use a noreply@...

@Nerea what are you talking about? Can you share a screenshot? 

Ooh, I see. the @mycompany.atlassian.net is not what I want, but it's progress.

I want to use notification email for sending automated emails.

good news! it is finally implemented, so no more weird workarounds for skipping spam

Hi,

I tested it and I have the same results as you, 6ef6f1467794.

I have now, automation@companyname.atlassian.net for the FROM option.

But, sadly, I had zero information about this change too.

It seems to work pretty well, fortunately !

Hi everyone. The issue of the generic FROM-address seems to somehow have been fixed in the Cloud version of Jira. At least I have experienced that all emails sent via Automation has been sent from an email-address specific to my cloud instance. This has been the case since yesterday (June 1st 2023). It is potentially a good thing for a lot of people, however a notice or warning would have been great, since I have spent time working around this by whitelisting the generic FROM-address no-reply@automation.atlassian.com in all systems that we have developed email integrations with using Automation. Does anyone experience anything similar?

Hi,

Like all the people in front of me, we need this feature "FROM", it's impossible to send email, it will obligatory fall in the Spam section.

Thanks for the help Atlassian team.

Cordially

https://community.atlassian.com/t5/Jira-Software-questions/Smart-Value-Project-Role/qaq-p/2362840

I ended up making my own php script that sends emails from an api request.... Jira automation will post to the php with json payload of data from tickets etc... then my mailer will blast out the email based on an html template.

works like a charm. i gave up on Jira built in plugins that promise todo this or its own built in functionality.

We are trying to move to the cloud after almost 10 years of use of Jira Software and 7 years of Jira Service Desk on premise but this defect is stopping us to do so. It is not affordable to deliver support services to an open community when the first notification goes directly to spam. We don't understand why Atlassian don't fix this, either way to change the reputation of the sender no-reply@automation.atlassian.com or implementing this feature that was already on premise. Also the alternative is using Legacy Automation that is being deprecated at the moment.

We are stuck in this situation with no alternatives from Atlassian. We were about to go on production next week.

We hope this gets done soon. Regards, Nerea.

+1

is it done yet?

+1

This feature would be very useful to my org as well.

https://codebarrel.atlassian.net/browse/ACF-10835

Any updates on this? We really need the option to edit Send From to the mail address with our managed domain instead of using this no-reply@automation.atlassian.com that all Jira accounts are using.

We need this option as well. Please look into it. 

A workaround I'm using, is to only comment on issues via Automation. Then, I configure a customer notification for the event "Adding comment". For language support I check the Request Language in Automation in an if / else if / else condition.

We need this option too! We are an international company and need Customer notifications in the different languages.

This is also deeply frustrating for us. I can only send plain text alerts which cannot include a clickable link to the issue.