Can automations be based on attribute update/change of an Asset?

[Calvin]

Hi all,

I want to create an automation that runs when an asset attribute boolean is set to true. I can't seem to find the attribute trigger, is "Object" updated/created/deleted the only ones available?

If I base it on "Object" Updated.

Then run an "If Object matches AQL" Where AQL = "ObjectType IN (xxx,yyy,zzz) AND boolAttribute = TRUE".

Would this be the same that I want to do with that single object, or is this going to run on ALL objects that fit the above AQL?

Cheers!

[Walter Buggenhout · Accepted solution]

Hi @Calvin,

If you use an Object updated trigger, the actions you specify thereafter in your rule would run on the object that triggered the rule. I am not sure why you would then want to add an additional JQL to run actions on other objects.

If you do want to act across multiple objects, you could do so by adding a branch to your rule and - in the given scenario - use an AQL branch to run on the objects returned by the search. This is, however, limited to maximum 50 assets (objects), as you can read in this support article.

Hope this helps!  

[Calvin]

Thanks Walter! I think I mispoke, I want to make sure my AQL doesn't accidentally run on every object by mistake. And it looks like it doesn't, it just runs on the one that was triggered which is great!

I guess that makes sense too, as I'd probably use a lookup object instead of an IF to get multiple and then branch that if I did need to go that route.

But indeed in this case mines much easier. Thanks so much for the link as well!

[Joseph Chung Yin]

@Calvin -

Excellent stated by @Walter Buggenhout

I am sure that you are already aware that Object related triggers are only available within Global Rules setup.

https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Object-trigger

Hope this also helps.

Best, Joseph Chung Yin

[Calvin]

Thanks mate! Yeah I made that mistake at the start for sure, when I couldn't find the AQL Branch. Appreciate the heads up :).

[Josh Schoenick]

But I see your correlation to Issue Field Updated, but for an Object right?

Do I don't need it to trigger on every object change, only if a single attribute changes.

For Example a Person Record has many attributes, but I only need this one automation to trigger if the "Department" attribute changes so that I can trigger a field on a Device to update to the same Department value.

If someone changes the Name of the person, this automation doesn't need to trigger.