Include the automation trigger field in Slack message description

Fouad El-Gendy May 21, 2024

I have an automation which sends a slack message when any of given fields (shown in attached screenshot) gets updated.

 

Is there a way to include the specific field that triggers each automation in the message? Instead of just a vague "Issue X has been updated."

Ex: If the Description of an issue is updated, I'd like the Slack message to say 'The Description of story X has been updated',.. same thing for any of the other fields

 

Untitled.png

1 answer

1 accepted

1 vote
Answer accepted
Kalyan Sattaluri
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 21, 2024

Hello @Fouad El-Gendy 

You can use the smart value {{fieldChange.field}} to reference the field name which was changed.

If you want to reference the values which were changed... you can look at the below link for available options. Hope it helps!

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#:~:text=issue_updated%20%3Aissue_commented.-,%7B%7BfieldChange%7D%7D,-Available%20anywhere%20smart

Fouad El-Gendy May 21, 2024

Works like a charm, thanks a bunch for the great help @Kalyan Sattaluri

 

Like Kalyan Sattaluri likes this
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 21, 2024

Hi @Fouad El-Gendy 

Adding to Kalyan's suggestions:

Not all issue changes trigger the Field Value Changed trigger (or the generic Issue Updated trigger) and so not all of them are detected in the {{fieldChange}} smart value for Jira Cloud...even though those changes appear in the issue change history when viewing an issue.

Some of these gaps are apparently due to errors in changelog handling (e.g., list fields such as Fix Version and Sprint), while others appear to be automation design choices where there is a separate trigger to detect changes to some fields.

 

I recommend testing for each field you wish to track to confirm they are detected as you need.

 

Kind regards,
Bill

Like # people like this
Kalyan Sattaluri
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 21, 2024

Thanks Bill. I keep forgetting to warn people of this behavior you have mentioned previously. I will try to clarify/state this point go forward!

Like Bill Sheboy likes this
Fouad El-Gendy May 22, 2024

Indeed Bill, I did check and they seem to work just fine, thank you for pointing that out!

 

On another note, I did create a separate automation to send any updates to the comment section of specific issues, so yeah, there's that.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events