Details
-
Type:
Improvement
-
Status: Done/Fixed
-
Priority:
Minor
-
Resolution: Fixed/Completed
-
Affects Version/s: 1.1
-
Fix Version/s: 1.2
-
Component/s: None
-
Labels:None
Description
Qill (seach criteria) display should always use 'label' rather than 'option' values. This includes boolean (yes/no) custom fields.
---- Original post from Jack Aponte ----
I've noticed two places in using CiviCRM where yes/no values are displayed or entered as 1 or 0. One place is when one creates a custom field and can input the default value - you can't write Yes or No, you have to enter 1 or 0. This also happens when advanced search results are displayed; for example:
No matches found for:
? Voter Info: Needs an absentee ballot? - "0"
? Voter Info: Needs a ride to the polls? - "0"
Now, this is all right for someone who's familiar with 1 equaling yes and 0 equaling no/null. However, users who aren't familiar with this might just be quite confused. It would be great if CiviCRM both displayed and allowed users to enter yes or no instead of 1 or 0.