since you weren’t precise about when the trigger should run i’m just guessing here:
If it should run on ticket creation your action is wrong (should be created not updated.
Currently it should run when you create the ticket and manually update it after that while keeping the state new.
If none of that applies to your case please give some more information about what you’re trying to achieve + some screenshots of your config would be helping.
You’re right. I should be more precise however there’s nothing complicated here.
Agent opens a ticket
Agent does nothing but uses update button
Now you can see on the list of tickets it has been updated but nothing else happens
At this point I’d like the ticket agent opened and updated by pressing update button to be assigned to him.
I did some further testing and it looks that pressing update button without any other changes does work only with one condition set (in my case Action is updated). If I add more conditions eg. Status is new the trigger works only when agent acutally does change something in this ticket using update button only isn’t enough.
So I need to find some other solution to speedup assigment process. Or shall I put this feature on request list? What’s your opinion?
Edit: Just a guess for the initial post:
Usually if an agent opens a new ticket the state gets updated to open. Maybe that was your problem for the trigger?