Can't seem to access changelog smart values to create a slack message.

[#1]

I have a JIRA automation setup to trigger whenever an update occurs on JIRA issues that have a specific label. The triggered rule sends a formatted message to a slack channel to bring awareness to the change via web hook. Here is my message that attempts to use smart values:

 *{{issue.key}}* – {{issue.summary}} was updated by {{initiator.displayName}}
{{changelog.fieldName}}: {{changelog.fromString}} → {{changelog.toString}}

The first line works perfectly. However, I cannot get anything to show up from the changelog. I can spit out the summary when using {{changelog.summary}} but not the individual fields.

ChangeItemBean{fieldId='summary', field='summary', fieldType='null', from='null', fromString='Testing Automation', to='null', toString='Testing Automation 1 2 3'}

I just get empty values so it looks like this

DEV-165 – Testing Automation 1 2 3 was updated by Yvette Nash
:  →

It does not matter what I update either; dates, fixversion, etc. Same result.

Any insights greatly appreciated.

Yvette Nash

[Bill Sheboy]

Hi @Yvette Nash 

For a question like this, please post images of:

• your complete rule,
• the action where you are accessing the changelog, and
• the audit log details showing the rule execution.

Those will provide context for the community to offer better suggestions.

Kind regards,
Bill

PS: Hi, community managers!  Would you please move this one from "App Central" to the Automation questions area?  Thank you!

[Yvette Nash]

[Bill Sheboy]

Thanks for that information, @Yvette Nash 

And...argh, someone keeps deleting / moving my replies!  (Perhaps the admins are in the middle of moving your question from App Central to the other area.)

Anyways...the {{changelog}} smart value requires specifying the field to use the {{fromString}} and {{toString}} smart values.  As workarounds, you could:

1. Store the entire {{changelog}} smart value as text with the Create Variable action, and then extract the pieces using text functions
2. Try using the {{fieldChange}} smart value instead