Important Update: Deprecation of Old Email Action in Favor of Enhanced Email Customization

[#1]

Hello Atlassian Community,

Camilo from the automation team here.

We're excited to announce a significant enhancement to our email automation capabilities. As part of our ongoing efforts to provide you with the best tools for your automation needs, we're introducing a new, more powerful email action that'll replace the existing one.

What’s Changing?

The current email action will be deprecated in favor of the new Send customized email action. This new action offers enhanced features, including:

• Custom domain support: Send emails from your own domain.

• Advanced formatting: Craft your messages in rich text formatting or HTML.

• Visual Enhancements: Add logos and banner images to your emails for a professional touch.

• Enhanced Security: Automated emails will comply with your organization's security policies.

See more details here: https://community.atlassian.com/forums/Automation-articles/Enhanced-email-customization-capabilities-available-in/ba-p/3031893

 

Why the change?

The new email action is designed to offer greater flexibility and customization, plus create better branded emails in automation. This also gives us a more robust infrastructure to add additional features in the future, such as attachments, email analytics, and more.

What do you need to do?

• Transition Period: Starting today, you may see a warning message on the current Send email action in your automation rules in Jira and Confluence, inviting you to replace the action with the new version. This will allow you to update your automation rules at your convenience.

• Automatic Migration: Throughout August 2025, our team will migrate existing rules to the new action, ensuring a seamless transition without data loss. Your emails and automation rules will continue to work, and when you edit a rule, you'll see the new action in your rules.

We're committed to making this transition as smooth as possible and are here to support you every step of the way. Feel free to ask any questions below.

Thank you for your continued support and trust in Atlassian products.

Best regards,

The Atlassian Automation Team

[Sami Shaik]

@Camilo Gomez 

Thank you for sharing this important update regarding the deprecation of the old email action in favor of the new "Send email" action. This certainly brings more flexibility and better configuration options to Automation rules.

I have a quick question - does the new "Send email" action support adding attachments dynamically during automation execution? For example, if a rule is triggered on issue creation or transition, can we attach files on the go as part of the automated email, either from the issue itself or generated content?

Appreciate any clarification on this - adding dynamic attachments would be a game-changer for many teams!

Thanks again for the update.

[Dirk Ronsmans]

Great!

Always a good thing to move to a single way of working instead of keeping both alive. Appreciate the fact that it will be an automatic migration as well!

[Aaron Geister]

This is great. I am happy to see this get updated.

[Tomislav Tobijas]

Nice! Just the other day, I used the new action and was thinking that we'll need to update all those rules that use the 'old one'
Really glad to hear it will be updated automatically :)

[Camilo Gomez]

Hi @Sami Shaik we are definitely working on supporting attachments on the email action. We will share more details in the next few weeks.

[Rick Westbrock]

Because I'm a curious nerd can you share how the team is migrating existing rules to the new action? I ask because I'm interested in how you can automate such a task.

[Mykenna Cepek]

WARNING: If your site has HIPAA enabled (as our does), then the new "Send customized email" component likely won't work at all.

Since the old/legacy "Send email" component has been disabled, this change breaks the ability for new Jira automation rules to send emails at all. Only rules still using the legacy component can send email as of right now.

Please cast a vote for AUTO-1959 if this affects you.

[Lindsay Bolan]

Adding on to what @Mykenna Cepek said, this is an extremely serious problem for HIPAA-compliant instances which needs to be fixed ASAP. I have several automation rules that use customized emails to communicate with external systems that we cannot set up Operations integrations for and that custom events w/ notifications cannot provide the information we need.

This change has effectively broken our ability to communicate with our security operations team.

[Camilo Gomez]

Hi @Lindsay Bolan @Mykenna Cepek thank you for flagging. We are actively working on a solution for this issue. I will share regular updates on the support ticket https://jira.atlassian.com/browse/AUTO-1959

[Mykenna Cepek]

AUTO-1959 has been converted into JSDCLOUD-17251. Please continue to vote for it and watch it for updates. It shows as Priority=High at the moment.