📣 Introducing Attribute Value Changed automation trigger for Assets

[#1]

Hi Atlassian Community! 👋

We have even more updates for you after last week’s releases of Unifying Assets across the Atlassian Platform. I’m excited to share we are also announcing a powerful new automation trigger: Attribute Value Changed. This trigger gives you fine-grained control over your asset management workflows, making it easier than ever to automate processes based on changes to specific asset attributes, without the need for complex workarounds.

Example Use Case

• Raise IT request: When the Status attribute of a Laptop object type changes to “Damaged,” automatically raise request for IT team to investigate and request new laptop.

• Onboarding: When an Employee object type with the Employee Status attribute is updated from Onboarding to Active trigger an automation rule that sends confirmation email to employee’s manager that the employee is fully onboarded.

• Compliance: When a Contract object type with the Renewal Status attribute is changed from “Pending renewal” to “Expired”, trigger an email reminder to the compliance team about renewal timelines.

How it works:

This trigger monitors a specific attribute of an Assets object and runs an automation rule whenever that attribute’s value changes.

Supported attribute types:

• IP Address

• Date

• Date Time

• Boolean

• Integer

• Text

• Float

• Status

Smart Values:

The following smart values allow you to configure the condition by identifying a specific state the attribute.

• {{attributeChangelog.(attribute name).from}} - what the attribute changes From

• {{attributeChangelog.(attribute name).to}} - what the attribute changes To

• {{attributeChangelog.(attribute name).changeType}} - returns the type of change in the attribute value: added/updated/deleted

• {{containerObject.(attribute name)}} - access any attribute of the object triggering the rule

See other smart values for Assets

Try out the new trigger today and let us know what you think in the comments!

---

FAQ

Q: When should I use this trigger instead of Assets Object trigger?
A: Use this trigger when you care specifically about changes in an attribute on an object, not just any change to the object.

Q: Does the trigger support all object schemas and object types?
A: Yes. As long as the object is in an Assets schema available in your site and you have permission to configure automation, you can select that schema and its object types in the trigger.

Q: Can I monitor multiple attributes with a single trigger?
A: No (Not Yet). Currently this trigger monitors a single attribute. For now, if you want to respond to changes on different attributes (for example, both Status and Owner), create separate rules with triggers for each attribute. We understand that users might want to monitor for multiple object attributes as part of a single automation rule. We are currently exploring making it possible. If you have a strong use case, we want to hear it!

Q: Will more Attribute types will be supported in the future?
A: Yes, we are planning to support more attribute type in future releases. Comment below the attribute type you would like to see.

Q: Can I trigger rules based on specific “from–to” changes?
A: Yes. Use smart values in rule conditions to check both the previous and new values of the attribute:

• {{attributeChangelog.(attribute name).from}} – previous value

• {{attributeChangelog.(attribute name).to}} – new value

Q: Can I detect what kind of change happened (added/updated/deleted)?
A: Yes. Use {{attributeChangelog.(attribute name).changeType}}.

Q: Does the trigger work with child object types?
A: No. Currently, object type inheritance is not yet supported in this trigger. This means that the trigger responds to changes on the chosen object type only and its attributes (own attributes and those inherited from its parents). But if the attributes of the configured object type are inherited by its child object types, attribute changes in objects of that child object type won’t be detected. If you have a strong use case for inheritance, we want to hear it!

Kind regards,

Michael Fedulov
Product Manager, Assets (Cloud)

[Daniel Santiago]

I'd like this automation to support object attribute types, not just the default attribute types.

[Josh]

@Michael Fedulov this is great to see! I'm with @Daniel Santiago on needing to have referenced objects available for this trigger. For CMDB scenarios, we're trying to leverage reference objects as much as possible rather than static values. For example:

• Application A is supported by Team 1. The Support Team value (a reference object) gets changed and now Team 2 supports Application A. We'd like to be able to alert our IT support teams when this kind of change occurs.

[JEFFREY SCHNEIDER]

@Michael Fedulov - This solves an issue I've been dealing with as I have some attribute changes I'd like to track. Would there be any way to track/filter the user (actor) who made the change? I'm not seeing that in the link provided.

[Michael Fileti]

Thanks for this. Please support the "Select" attribute type next!