Used Zammad installation type: (source, package, docker-compose, …) package
Operating system: Linux Debian 10
Browser + version: Firefox, Chrome, Linux
Expected behavior:
New custom boolean ticket attribute created, default value marked via bullet. Then saved.
Actual behavior:
Attribute works well. Some days and tickets later when opening attributes config, the default value bullet was not setted. Changing the default value to the opposite of the primarily setted value fails.
Additional some strange behaviour in ticket editing occurs, when this attribute is setted mandatory: Agent can’t change the value. Message: “xyz-attribute is mandatory”. When not setted mandatory, changing the value works well.