Jira Automations: Edit object attributes vs edit asset field attributes

[Haig Aboyan]

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:

[Pier-Olivier Tremblay · Accepted solution]

you need to use the AQL Branch if you want to edit the objects.

Branching on a smartvalue will only let you read!

[Haig Aboyan]

I also realized that I dont want to update the "Next Performance Review Date" via "now(+180d)" because that updates the attribute to a 18p days from today. I want to add a 180 days to the currently stored date. Any suggestions on how to achieve this?

[Kai Becker]

Hi @Haig Aboyan 

could you post a screenshot of the whole rule?

[Haig Aboyan]

Hi @Kai Becker

[Nathan Allen]

I'm running into this same problem. Did you ever find a solution?

[Kai Becker]

@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:

[Nathan Allen]

@Kai Becker I don't have any option to branch on AQL, not sure where you're finding that.

[Pier-Olivier Tremblay]

The rule needs to be global to make it appear !

[Nathan Allen]

Perfect. Thanks!

[Kai Becker]

Thanks @Pier-Olivier Tremblay for the addition. Forgot to mention that. :)

[nicolae_cotan]

Hello, i need the same use but for users. I need to edit and object attribute called User and fill it with the atlassian user.

Do you think this would work?

[raphael_lopes]

how to edit attribute with atomation when a filed have more than a object?

[raphael_lopes]

[mb]

Thank you so much @Pier-Olivier Tremblay !

It's incredible to me that I had to switch to scope "global" and then back to "single project" after enabling the AQL Branch. Otherwise I wouldn't be able to use the "forms submitted" trigger as it's not available in global rules!

[Pier-Olivier Tremblay]

@mb yeah I don't get it either why it works like that x)

[mb]

Seems like a bug to me, but I got kind of tired of raising bugs because neither feature requests nor bugs seem to get fixed/introduced in a reasonable time :(

[Sidney Dizon]

@raphael_lopes were you able to find an answer to that?

I am having the same problem

[raphael_lopes]

Yes, I did, my automation looks like this.

[Luke McDonnell]

Just like to say thanks so much for sharing this! I had been trying to figure this out for the past day and the AQL in Global worked perfectly!