Update Trigger not actived when only editing Ticket fields

dbayer · January 11, 2022, 8:28am

Infos:

Used Zammad version: 5.03
Used Zammad installation type: (source, package, docker-compose, …) docker-compose
Operating system: Ubuntu 20.04
Browser + version: Firefox 95

Expected behavior:

When I edit a Ticket Field and then hit update, I expect the Trigger (Action is Updated) to trigger. The execution is a Webhook.
*

Actual behavior:

The webhook is never called. But if I add an article and hit the Update button it is called.

Steps to reproduce the behavior:

Described above
*

MrGeneration · February 25, 2022, 12:50pm

Sounds like you’re affected by this bug:

github.com/zammad/zammad

Trigger is not executed when Action is Update and Attribute is Value

opened 10:38AM - 20 Jan 22 UTC

closed 10:54AM - 14 Jun 23 UTC

mantas

bug trigger ticket verified

### Infos: * Used Zammad version: 5.1 * Installation method (source, package, ..): any * Operating system: any * Database + version: any * Elasticsearch version: any * Browser + version: any * Ticket: #10100015 ### Expected behavior: * Create a trigger with condition `Ticket Action: Update` and `Attribute: value` * updates any ticket value * Trigger is executed ### Actual behavior: * Trigger with condition `Ticket Action: Update` and `Attribute: value` * Updates any ticket attribute, but not `Attribute` * Trigger is not executed even though `Attribute` matches `value` * Trigger is executed only if `Attribute` is updated to match `value` ### Steps to reproduce the behavior: * Create a trigger with condition `Ticket Action: Update` and `Attribute: value` ### Possible solutions **A**: * clarify that using `Ticket Action: Update` and `Attribute: value` will check if the `Attribute` was updated **B**: * change behavior that using `Ticket Action: Update` and `Attribute: value` will check only the value of `Attribute` * this would be a breaking change **C**: * Separate conditions into Ticket selector and Action analyzer. * Ticket selector would check if ticket matches given values (as in **B**) * Action analyzer would check if the change itself matches given conditions (as in **A**). * This may affect Scheduler, Macro and other conditon-able tools as well Yes I'm sure this is a bug and no feature request or a general question.

system · June 25, 2022, 12:51pm

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.