Trigger to "Execute changes on objects" not working for client

[retrodans]

Infos:

• Used Zammad version: 6.4.0
• Used Zammad installation type: Docker
• Operating system: Linux
• Chrome/Opera

Expected behavior:

• WHEN a trigger tries to change a custom field
• AND it is a client that triggers the trigger via ticket created/updated
• THEN I expect the field to change

Actual behavior:

• The trigger only triggers for my admin user, not clients

Steps to reproduce the behavior:

• Create a custom field (in my case, it is a single choice dropdown)
• Create a trigger for when ticket is created/updated
• Set this trigger to change the single choice select list
• Test this as admin (it should change)
• Test this as a client (it is not updating)

[retrodans]

Here is a screenshot to better show the trigger config, and you can also see the field I am trying to set is core one, so this isn’t an issue with custom fields either.

[MrGeneration]

How exactly are you testing this…? Are you just hitting the “update” button and hope for the best…?

[retrodans]

Closing, as can no longer replicate, and various too much has changed since January to properly narrow down the cause (eg. security and server updates).