JSM automation re-assigns the ticket without me telling it to do that

[Alain Kovacs]

Hello all,

as the title says, I think that I have found a behavior that's a bit strange, maybe a bug? I have the following automation. As you can see, there is not "component" to reassign the issue.

But when the automation runs, the resolution is set correctly, the status is updated correctly, but for whatever reason the assignee is also changed to "Automation for Jira". Why does it behave like this? I want the assignee to stay the same as before closing

I have now modified the "Actor" of the rule (before it was "Automation for Jira", I have now modified it to "User who triggered the event", but I'm not sure how or whether this will work, since the trigger is an SLA breach..

[Alain Kovacs · Accepted solution]

Ok.. I think that I might have just solved it myself.. So I had a post-function which assigns the issue to the actor that closed the issue.. (this was done a long time ago to avoid issues not having assignees as my jira users tend to forget to assign themselves..) I hope this will solve my "problem"

[Marc - Devoteam]

Hi @Alain Kovacs 

Your change on changing the actor should solve this.

[Alain Kovacs]

HI Marc, I'm fairly sure that I solved it myself (see my comment above), but nonetheless, as actor I'd like to be able to select the "assignee", right now it's only the trigger user, but I don't know who that is if the trigger is an SLA-"automation"