- Used Zammad version: 2.6
- Used Zammad installation source: (source, package, …) package
- Operating system: Centos7
- Browser + version: any
Expected behavior:
- Boolean object (e.g. for organisation) should be visible independet of its value
Actual behavior:
- The field disappears if it’s set to false
Steps to reproduce the behavior:
- Create a new boolean object (in my case “subscription” in organizations)
- Set the value to false for an organization
- Create a ticket for this org and have a look at the organization details → The “subsription” field ist not visible
Subscription set to True:
Subscription set to False:
Hi
Sorry for bumping… I just wanted to know if it this the intended behaviour to hinding “false” boolean fields or am I facing a bug?
thanks and best regards
Kay
I could reproduce this, but am not sure if this is really intended.
My guess is that it’s intended (“why should I display something that’s set to false”) - but maybe the devs didn’t think about the option that someone would use booleans within customers and organisations.
@anon29869905 could take a look if this is intended, but he’s on holiday. 
As a workaround you could use a dropdown (select), this is working just fine and can contain a “key”.
Hope that helps
IMO this is a bug. Please file an issue and we will handle it 