Infos:
- Used Zammad version: 5.1
- Used Zammad installation type: package
- Operating system: CentOS 8
- Browser + version: FireFox 99.0.1 (64 bit)
Expected behavior:
- Should save conditions state correct.
Actual behavior:
- After adding second, third (and so on) conditions, previous conditons randomly changes
The goal is to set one option from custom object list, depending on the ticket source. Very usefull for statistics in our company.
For condition i am trying to use article type (may be it is not the right way, correct me if its a mistake)
Steps to reproduce the behavior:
- Add first trigger (Conditions for affected objects Article:Type → phone & Action->is created & Execute changes on objects → source: call)
- Add second trigger (Conditions for affected objects Article:Type → email & Action->is created & Execute changes on objects → source: email)
- Open then first trigger and you wil see that source: call cnanged to source: email
I’ve made a screencast