nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation to send slack message on 2nd and subsequent changes

Lori Milam

I need to write an automation for when a custom field changes to send a slack message only on 2nd and subsequent changes. For example, field name is Quarter committed. It remains empty for a while. When they are ready to commit to a quarter they enter a value. No slack message should be sent. After this, then any change including back to empty needs to send a slack message. Is there a way to tell when the value has changed the first time without checking "empty"? Like looping through the history of a field?

Accepted answers

Bill Sheboy

Hi @Lori Milam

If your rule is triggered on a change to the field, you could try using the {{changelog}} smart value and test if the {{fromString}} is not empty. That would indicate the value changed.

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog--

If this does not help, please post an image of your complete rule and the audit log details showing the rule execution. These will provide context for the community to offer better suggestions.

Kind regards,
Bill

All comments

Mohanraj Thangamuthu

Hello, Good day. What is the field type, we can try to use different if/else condition in the rule based on field type.

Bill Sheboy

Hi @Lori Milam

If your rule is triggered on a change to the field, you could try using the {{changelog}} smart value and test if the {{fromString}} is not empty. That would indicate the value changed.

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog--

If this does not help, please post an image of your complete rule and the audit log details showing the rule execution. These will provide context for the community to offer better suggestions.

Kind regards,
Bill

Lori Milam

Hi @Mohanraj Thangamuthu it is a Select List (single choice). The trigger is when value changes.

Lori Milam

Hi @Bill Sheboy one question. Using the changelog fromstring only shows me what it is changing from for this one change, right? This wouldn't necessarily tell me if it has changed back to empty previously, so not the very first change to this field. Am I thinking about this correctly?

Bill Sheboy

Well done thinking of the different cases! They would be this:

empty value => non-empty value
non-empty value => a new non-empty value
non-empty value => empty value

You could use the current value and {{fromString}} to test with if / else conditions and handle the paths needed.

Lori Milam

Thank you. I have this part figured out. The part that I'm stumbling on is if the user goes from non-empty value to empty value, then assigns the empty value to non-empty value a second time, they want to receive the notification.

So the only time they don't want the notification is if the field hasn't been touched at all since creation and they change it for the very first time. Any changes after that they want the notification.

So it's like I need to be able to look back at the history of the changes or I need to flag it in some way at creation.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud