Earn badges and make progress
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
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Come for the products,
stay for the community
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Jira Automations: Edit object attributes vs edit asset field attributes
I am currently working on an automation rule that edits object attributes. After I perform the object lookup I perform the action and its at this point where I am running into issues. You can see the action below which is is an "Edit object attributes" action and this edits the "Next Performance Review Date". And when I run the rule it runs successfully, but only because it outputs the following message "Edit Assets field attributes, No issues were found, stopping the rule". The message is incorrectly outputting that I am running an "Edit Assets field attributes" action when in reality I am running an "Edit object attributes" action.
Additionally, the error message state that "no issues were found", which is confusing because no issues are being edited/updated as a result of this action, only the object that has been looked up should be updated. I'm not sure if this is a bug or if there is a work around, but I'm looking to see if others have had similar issues and how they've worked around this.
Action being performed:
Message in audit log:
2 answers
1 accepted
@Nathan Allen, @Haig Aboyan you need to branch on AQL, otherwise the rule will focus on the issues instead of the objects. Please put the AQL from lookup objects into the branching part.
Here is a simple example:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.