---
title: "Send email upon Release status change"
canonical: "https://help.releasemanagement.app/space/RMC/2921889979/Send%20email%20upon%20Release%20status%20change"
format: markdown
---
> Macro (include)
# Troubleshooting?
> ℹ️ Have issues running Release Automation rules? Please check our troubleshooting guide - [https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2522284033/Release+Automation+for+Jira+Triggers+Conditions+Actions#%F0%9F%86%98-Troubleshooting-Automation-Rules](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2522284033/Release+Automation+for+Jira+Triggers+Conditions+Actions#%F0%9F%86%98-Troubleshooting-Automation-Rules).
# Topics
> Macro (toc)
# Introduction
In Release Management App we allow to send Slack/Teams notifications upon release change via [https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2522284033](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2522284033). We do not support “**Sending Emails**“ as possible actions, but Jira Automation does. Therefore, it’s possible to create an automation rule with Jira Automation bridge to pass the required payload and construct the message you want to send.
Let’s see how we can do it.
# Step 1: Create Jira Automation rule
Navigate to Automation in Jira and **create** a rule.
Select **Incoming webhook** as trigger.
*(!!!) Copy Webhook URL and Secret, you would need it in Release Management.*
Select “**No issues from the webhook**“.
Add “**Send email**“ as action.
*Put some temporary Subj and Body for now. We will come to it later.*
Click **Save**.
# Step 2: Create Release Automation rule
Click **Settings** on your Release board and select **Automation**.
**Add **new rule.
Give it some **Name**.
Select **Scope** - Version or Package
Click on **Triggers **and decide when you want to fire up and email. For the sake of example let’s select version move (=status change).
Add condition if you want to fire email only if the version move to a specific column(s).
Add “**Invoke Jira Automation**“ as Action.
Give it some **description**.
*Copy the ****URL and Secret from Jira Automation ****(the one you copied on previous step).*
Click “**Hide secret**“ to assure that it’s not exposed.
Click **Save** to action & **Save **to rule.
# Step 3: Compose the message and turn on
Now let’s get back to Jira Automation rule an open it for Edit.
You can now use the data passed from Release Management to update the Subject and the Body the way you like, for e.g.
> ⚠️ **Subject**
> ⚠️
> ⚠️ Version {{**webhookData.entityName**}} is ready for UAT
> ⚠️
> ⚠️ **Body**
> ⚠️
> ⚠️ Hi there,
> ⚠️
> ⚠️ We would like to notify you that version {{**webhookData.entityName**}} was moved to {{**webhookData.statusName**}} status.
> ⚠️
> ⚠️ For more details: {{**webhookData.entityLink**}}
> ⚠️
> ⚠️ Kind regards,
> ⚠️
> ⚠️ Release Management Team
> ⚠️
> ⚠️ **More details:**
> ⚠️
> ⚠️ For all available fields you can use from Release Management check the following: [https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2522284033/Release+Automation+for+Jira+Triggers+Conditions+Actions#%F0%9F%A4%96-Action%3A-Invoke-Jira-Automation](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2522284033/Release+Automation+for+Jira+Triggers+Conditions+Actions#%F0%9F%A4%96-Action%3A-Invoke-Jira-Automation)
**Turn on** the rule.
# Step 4: Troubleshooting automation
If you are triggering the action but not necessarily see the expected output (e.g. email being sent)
**1st Navigate to Release Automation rule**
Click on **History. **Check the last item and select “**Show more**“.
Scroll to see any reason if the status is **Failed** to help you troubleshoot.
**2nd Navigate to Jira Automation**
Click on **Audit log. **Get the latest relevant item and select “**Show more**“.
Scroll to investigate the issue if status is “**Some Errors**“.
> Macro (include)