Setup automation for release - when a release date is set then fire a slack message

[Ivan_He]

Hello everyone,

I am trying to set an automation when a release date value is selected for a release, it automatically send a message to a slack channel with the release date

Below is how I have the automation set up. It works, and I get a message sent to the Slack channel.

However, if I update other fields (for example: start date) the automation will send a slack message. If I mark the release as archived the automation will send a slack message.

I ONLY want to send a message if the release date is set or if it's updated. I believe the issue is due to the trigger when Version is updated, and if the due date is set then any time i update a field the automation will trigger.

Any idea on how I can fix this?

[Trudy Claspill]

Hello @Ivan_He 

That is not possible at this time.

This suggestion seems to be related to what you want; the ability to detect which field changed in the version (as well as the previous and new values for the field).

https://jira.atlassian.com/browse/JSWCLOUD-27005

[Ivan_He]

Thanks for the input Trudy. The URL above sounds like a fix version is being applied to multiple projects and the automation is to update the field from one project to another. 

I'm looking to detect if a specific field within the release is updated. If and only if that field is updated then I want to send a message to users about that field. 

Example

Create a release (fix version) in project A

Create an automation to notify users via Slack when the Release date field is populated or updated in Project A 

Expected results: When I select a date for the release date field, a notification is sent to slack. When I select a date for another field, say start date, then NO notification is sent

Actual result: 

- When I select a date for another field (ex: Start date) a notification is sent to slack.

- When I select a date for the release date field a notification is sent

[Trudy Claspill]

Detecting which field changed in a Release Version is not possible.

The issue I referenced uses the term "fix version" within it, but the "Version Updated" trigger concerns changes to a Release Version rather than changed to the Fix Version field within issues.

What the Description in that issue describes is trying to maintain identical Release Version information in two separate projects. They are using "fix version" to refer to the Release Version entities, not to the Fix Version field.