Status condition in Trigger not working

Technical assistance
1

Infos:

  • Used Zammad version: 6.1.0
  • Used Zammad installation type: package
  • Operating system: Ubuntu 20.04.6 LTS
  • Browser + version: Google Chrome Version 116.0.5845.188

Behavior:

Since the latest update I’ve already mentioned a slight difference when you use custom status. See here

A few days later I discovered that our triggers were no longer working. Therefore I did my troubleshooting and found out that this is caused due to the status. I don’t know how this is related but I can confirm that in every trigger we use, the condition isn’t working anymore. Is there a way to update/reindex the status, or what would be a reasonable approach to fix it so the status is recognized again in the trigger conditions? I would appreciate any contribution

Steps to reproduce the behavior:

image
image963×637 34.9 KB

2

Checking for select values without value is rather a unlucky configuration. If possible and suitable, consider checking for the value the ticket is not supposed to have during your trigger run.

Like “attribute - is not - value”. This might help in these scenarious. Because ‘-’ technically is not a value. You’d look for 2not set" actually.

Upgrading to Zammad 6.2 might also help. The trigger context currently experience a lot of devleopment attention.

3

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