Scheduled Automation for updating Jira User Profile

Bekkah Crisp March 18, 2024

Has anyone been able to get this How to update user type attribute of an Asset objects using Automation after Import | Jira | Atlassian Documentation to work with a "schedule' trigger? 

I have it working up to the web request, and it says it is running successfully. I have tested the URL in Postman and can see that it is pulling the Account ID for the users in the log.

I added an audit log step to show what the AAIDUser was pulling for {{webResponse.body.accountID}}, and it is blank. 

I am guessing this is because my AQL query returns more than one email address and the web request isn't looping through each variable?

Any ideas on how I can use the schedule option vs the 'when created'??

1 answer

0 votes
Kris Dewachter
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 19, 2024

Hi @Bekkah Crisp ,

I have implemented this solution once. But I used the "When object created" trigger, not the scheduled trigger.

If you use the scheduled trigger, I presume you loop over each found object, an perform a API call per user object.

Best regards,

Kris

Bekkah Crisp March 19, 2024

Hey Kris,

That is what I assumed also, but no luck :/ 

Thanks!

Kris Dewachter
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 21, 2024

Hi @Bekkah Crisp ,

I have been testing with this a bit, but unfortunately I have also not been lucky getting an automation rule to loop over an "Lookup Objects" result, and perform a webrequest for each result.

It seems to work fine when you use the "Send Email" action instead of webrequest.

 

So i'm also curious to see if there is a solution for this. For now, I will stick to my "Object Created" trigger.

 

Best regards,

Kris

 

 

Bekkah Crisp March 21, 2024

Hey Kris,

I actually ended up getting it to work. For me, it ended up being an auth issue. 

Screenshot 2024-03-21 at 12.49.40 PM.png

Like Kris Dewachter likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events