You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I do not know how you are supposed to specify what object you are changing the attributes on. It makes no sense why it would give an attribute to set but no object to specify. Any thoughts?
Hi Tristan, with the introduction of Insight Cloud into JSM Automation, there are now two classes of rules:
The new "Edit Object" action only works in the first class of rules. A typical rule is to set a default status for an object, eg.
Object-based rules use {{object}} - except within branches, which will introduce an {{issue}} smart value to work with. You can change between the rule classes pretty easily by changing the trigger.
I do bulk updates of objects by adding "Action" and "Result" free-text attributes to object types then using this rule:
Then I just need to do a bulk update of objects and set Action attribute to "Update user details" to trigger an update of user objects from Okta.
Tip: If you can't see the object-based actions, you're probably in the Project Automation Administration page. All object-based rules must be global, so you have to go to the Global Administration page to add object-based rules and actions.
(Edit: fixed a logic error in the automation above)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alex van Vucht (GLiNTECH) ,
Just a follow-up question here, do you know if it is possible to apply Edit Object action on a specific object other than the object triggering the rule? I mean either by selecting it manually or resulting from an IQL query.
Thanks. I appreciate your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Amr HamzaNo, not yet. See https://jira.atlassian.com/browse/JSDCLOUD-10023
I have posted a kind-of workaround at https://jira.atlassian.com/browse/JSDCLOUD-10002 - this can help in some cases,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Alex van Vucht (GLiNTECH) ,
I'm trying this first class of rules that you suggested but its still not working, the log still doesn't know where to got for editing the attribute.
can you pleas instruct me on how this we should be done?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
One more addition from us. You can use both Object Trigger and AQL Branch for performing edits on objects. Here are 2 use cases and the automation rules with details as examples:
Use Case 1: Update objects instantly when they are created and set the Jira User.
Use Case 2: Update objects periodically (i.e. once a day or an hour) and set the Jira User.
Hope that these will also help.
Pio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.