Automation rule running more than once for a single event

[Simon Bramfitt]

I have a simple automation than is triggered whenever an issue is updated.

If the assignee is blank it updates the assignee field to make it the user who triggered the event.

For some reason, the rule is being triggered two or three times whenever an issue is updated with the status being returned as Success, No Action Performed, or Some Errors.

 

Any ideas why?

thanks 

[Mark Segall · Accepted solution]

Hi @Simon Bramfitt and welcome to the community!

Issue Updated is very generic.  If the user is making multiple updates to an issue, it can trigger it to execute multiple times.  I would recommend instead triggering on either issue transitioned or Field Value Changed instead.

[Tansu Akdeniz · Accepted solution]

Hi @Simon Bramfitt 

Welcome to the community.

SOME ERRORS -> User can not be assigned. User who triggered the event doesn't have Assignable User permission in this project.

NO ACTIONS PERFORMED -> If assignee exists in the ticket, automation starts but since assignee is not empty, it doesn't take any action.

*As an alternative to automation, you can use condition or post-function in workflow to ensure assignee is not empty or to assign to current user automatically.

[Simon Bramfitt]

Thanks @Tansu Akdeniz 

I'm starting to think that this is timing related - the user triggering the script can manually assign the ticket, and the automation reports an error only when the user performs that step. 

I'm still very new to JSM, so automation looked to be the easy way out.  I'll have to dig deeper if I'm going to follow your suggestion.