nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Accessing Rule Initiator User in JSM Assets Object Update

Amandeep Singh Main

My JSM Assets Schema Objects can be updated manually by users, and also by a dedicated API (Fixed User API Token). I have created a rule in Global Automation that is triggered whenever Objects in my Schema in JSM Assets is updated. I want to trigger it conditionally: only if the User who triggered the Rule (ie updated the object) was not my Bulk API User. I tried with

{{initiator.displayName}} {{initiator.emailAddress}} {{initiator.accountId}} but none of them works.

I also tried updatedBy != '"" , but doesn't work. How do I get the initiator of Rule?

Accepted answers

All comments

Bill Sheboy

Hi @Amandeep Singh Main

If you write the entire smart value for {{initiator}} to the audit log, what do you see when the rule triggers?

Kind regards,
Bill

Amandeep Singh Main

Its blank.

Andrea Robbins

Hi @Amandeep Singh Main

That seems to be available only for work item triggers. You have two options:

1. Either use the REST API to get the object history to see who was the "actor": https://developer.atlassian.com/cloud/assets/rest/api-group-object/#api-object-id-history-get

2. Just provide the Object Developer role to the Bulk API User - this way everyone else just has a view (user role) permissions, so you don't even have to create this automation rule

Hope this helps,

Andrea

Amandeep Singh Main

Our use case is not fulfilled by not allowing others to update so option 2 is not feasible.

Regarding Option1, it will trigger 1000s of API calls for each update that bulk API does just to capture 10-15 manually edited values per day.

Any other solution?

Andrea Robbins

Our use case is not fulfilled by not allowing others to update so option 2 is not feasible. - what is the use case? Maybe I can help by understanding the use case better - I do understand the cause for concern if the bulk api user is making that many updates.

Amandeep Singh Main

Python script updates the JSM Assets with data every few hours. It will update every field except some fields that are Manually Updated. We are tracking those field names in a attribute - Manually Changed Fields.

We want the rule to capture if the most recent change is by API or a user and then decide the next steps.

Everything is ready and working except we aren’t able to capture the user who triggered the rule.

Arkadiusz Wroblewski

@Amandeep Singh Main

Will that maybe helpful for you

https://support.atlassian.com/jira/kb/find-the-previous-attribute-values-when-using-object-updated-trigger-in-an-automation-rule/

Kevin Gérard

We're using Assets as a CMS system, It's using automation to synchronise the data to Atlassian users, it's how we manage our JSM customer base.

This has been an issue for us too, i'm currently actually busy rewriting these rules.

What we do now is get the object history from the API, as suggeted above. we can dedact the actor and change from there.
I think using this, u don't actually need to store the 'manually updated' fields in a seperate field, as you can fetch them from the history output.

note: you should ignore the history log where type = 0, that is the 'create' event.
we use this one to fetch the object creator.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management