Bug report. Self created ticket object boolean attribute issue


  • Used Zammad version: 4.1.0
  • 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.

Steps to reproduce the behavior:

Sounds like you’re describing this bug:

If not, please use the steps to reproduce to help me understand the required steps better and easier.

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