Improve "Send email" action - add support for e-mail templates, emailing over 50 users, send to specific user using smart value, send to all users in an organisation, default to/from addresses, email to a specific user

With the change from legacy automation to the new automation there doesn't appear to be an email template to send an email. We set these up to ensure consistent formatting of all emails and just enter the content in the automation.

When using the legacy automation the email template set up in Customer notifications is used (this includes content and CSS formatting). However with new automation the send email action doesn't appear to use this template.

Instead the emails seem to get some mime formatting surrounding the email content and html tags (eg <br />) included in the email. I have set the emails to send as HTML and enabled convert line breaks to HTML line breaks.

Please add usage of email templates to the send email action

***

When sending emails from automation rules, we can currently change the name of the sender, but not the "from address", which remains greyed out, and is "no-reply@automation.atlassian.com. 

This poses an issue for several reasons : 

• the customer can actually reply to the email that is sent, and this is something that we can customise so that the customer can get in touch with us if needed.
• given that the address is the same across all Atlassian instances, anyone can set up an automation email, which poses a security risk. 
• we are using a custom domain for all the other notifications to clients set up in the portal, so the automation emails we have set up being sent from another email juxtapose the custom domain, and are potentially blocked by our clients' email filters. 

***

Ability to add multiple emails for Send Mail automation action - 

Currently, when creating a Send Mail action on your automation rule. You have to enter each 'To' email address separately. I currently have 55 to add and have to do it 4 times, but if we had the functionality to copy, I could have done it once and simply copy and pasted the action.

If you enter something like this; email1@test.com; email2@test.com; then it simply combines it into one email address and nothing happens when you run the rule.

It would be good if we can simply copy a list of email address and paste into the To field and it would separate each email. On MS Outloook, using email1@test.com; email2@test.com; separated the email so maybe the same functionality can be added?

Improvements

• Add default Reply To/From addresses
• Support for email templates These should probably be re-usable across projects and support things like header/footer/body.
• Also provide the ability to have email messages based on locale.
• Send Email action will only send to the first 50 users in a group (if group is greater than 50) - The Send Email action will only send to the first 50 users in a group with size > 50. This limitation is currently coming from the downstream Identity API which imposes a 50 user limit. We should send to all users in the group.
• Add organisations field as option in the "to" field for send email action
• Add an option on the email action to respect the JSD option for users to not be notified - If the "Reporter" clicked "do not notify" in the client portal they shouldn't be emailed
• Improve documentation on the email action (esp recipients fields) - There are some nuances in what we show in this list and its not actually obvious what the options represent (e.g. which ones are fields, which ones are built-in values, which ones are us trying to be helpful). Would be good to add some more documentation around this
• Ability to pick rule owner for the email action recipient field - So you don't have to type in their email address and can copy rules more easily.
• Allow for email action to have the content to be translatable -
  This is what JSD has https://confluence.atlassian.com/servicedeskserver0311/managing-service-desk-notifications-946628493.html
• Allow send to a specific user - So you can search for a specific person in the drop down
• Improve automation notification emails: A4J e-mail to look like JIRA's e-mail - This could be good to have for default notifications and also for the "Send e-mail" action mail messages.
• use 'Email from' setting from General settings in Jira
• Ability to exclude the initiator in 'Send e-mail' action - The send e-mail action makes it possible to send to groups etc and it would be good to exclude the Initiator of the event from this. SD notifications do this.
• Use same threading as JIRA for outgoing emails - Automation emails going to spam (make A4J e-mail look like JIRA's e-mail)
• Improve documentation on the email action (esp recipients fields) - There are some nuances in what we show in this list and its not actually obvious what the options represent (e.g. which ones are fields, which ones are built-in values, which ones are us trying to be helpful). Would be good to add some more documentation around this
• Send email action to a "Project lead"
• Add a configuration option to fail a rule if email delivery fails or is unknown - Add a configuration option, likely needs to be added to the email action(s), to fail a rule if email delivery fails or if it is unknown. Unknown means SES fails to respond to our send request or reports an unknown delivery status itself after a timeout. https://jira.atlassian.com/browse/JRACLOUD-76964
• Team managed custom fields are not pickable in Send email action
• Ability to change the FROM email address to meaningful address.
• Create email allowlist config to automation action Send Email