📣 Introducing Attribute Value Changed automation trigger for Assets

[Michael Fedulov]

Hi Community! Thank you again for all the feedback around having changelog smart values support the User attribute type. We completely understand how valuable this would be and the variety of use cases it could unlock. Unfortunately, at this stage we can't share a specific timeline or commitment for further enhancements to this trigger. That said, your comments here are being collected and fed directly into our prioritisation for future improvements.

In the meantime, please refer to a workaround avaliable to fetch the “from” and “to” values in a different way: Find the previous attribute values when using "Object Updated" trigger in an automation rule | Jira and Jira Service Management | Atlassian Support

Please keep sharing your use cases, this input is really helpful for shaping what we do next.

[Rune Rasmussen]

@Michael Fedulov Could you log, or link to, feature requests in JAC for us to watch and vote for while we hope this won't be another one of those almost-good things that gets left behind for 5-10 years?

[Bill Sheboy]

Hi @Michael Fedulov 

For asset and object-attribute related triggers, are there events raised such that the rule's {{initiator}} smart value reflects which user made the change?

Thanks, and kind regards,
Bill

[Sean Meenaghan]

I really appreciate the availability of this automation trigger.

I wanted to share my desire for supporting multiple attribute values for the trigger. For example, I have an automation rule for keeping my User object's Full_Name (label) attribute in-sync with the First_Name and Last_Name attributes of the User. If either First_Name or Last_Name is modified, I want the automation rule triggered to update the value of Full_Name to reflect the change.

I understand this can be done using 2 automation rules, each triggering for the First_Name and Last_Name attributes separately, but this requires updating both automation rules and keeping changes to either rule in-sync with each other. Furthermore, if the Full_Name attribute is directly modified, I would also want to trigger the rule to ensure it is actually the concatenation of the First_Name and Last_Name attributes.

As a full workaround to this, I may continue to use the Object Updated trigger, and use smart values to check the `attributeChangelog` to check if any of the 3 attributes were changed to trigger the rule.

Thank you!

Edit: while both my comment(s) still apply, I changed my automation rule to better support my use case:

• Trigger: Object Updated
• Conditions:
  • objectType = User
  • "{{object.Full_Name}}" does not equal "{{object.First_Name}} {{object.Last_Name}}" (without the quotes, of course)
• Action: Edit Object Full_Name field to: {{object.First_Name}} {{object.Last_Name}}

This keeps the First_Name and Last_Name fields synced with the Full_Name field regardless of which field(s) were modified and triggered the rule.

[Sean Meenaghan]

In addition to my previous comment: it would be good if the {{attributeChangelog}} smart value could be used in all other Assets triggers, such as the Object Created/Updated/Deleted trigger.

I did try to use the attributeChangelog in the Object Updated trigger, but I receive no value. I tried storing it in a variable and/or logging it, but there is no value present. My assumption is that attributeChangelog is only available in the "Attribute Value Changed" trigger.

The reason I am using it is because I am using conditions to only execute actions if a change was made to any 1 of 3 different attributes. If any of those 3 attributes were modified, the actions are triggered. If not, then no actions are taken.