Problem/Motivation

Was working on the comment module docs and noticed under the field type options to add onto the comment form "Boolean" is part of the list...talk about non-user-friendly UI text. I'm pretty sure my proposed label "Simple yes/no option" (based on the description already in the list module file) will be contested, but I'm moreso filing this just to note that it probably needs to be changed.

(Also maybe "float" needs to be modified but I don't have a good enough sense to warrant filing an issue there.)

Steps to reproduce

Proposed resolution

Closing as won't fix based on usability review, See #30
Change the label of the Boolean field type from 'Boolean' to 'Yes/No option'.
Before

After

Remaining tasks

1. Decide if this change should be made.

User interface changes

Yes, the label for the Boolean field.

API changes

Data model changes

Release notes snippet

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

aspilicious’s picture

Version: 7.0-beta2 » 8.x-dev

Moving this to 8.x

I can see why boolean is not that user friendly. But I don't think we need "simple" in the sentence.

aspilicious’s picture

Status: Active » Needs review

Can use a review

Status: Needs review » Needs work

The last submitted patch, list_boolean.patch, failed testing.

arianek’s picture

looks like i might have to dig into d8 and reroll ;)

yoroy’s picture

Status: Needs work » Needs review
FileSize
2.4 KB

I need some practise too…

aspilicious’s picture

Store or stores not both :)

I prefer stores.

yoroy’s picture

True

arianek’s picture

I think the revised labels (from comment 7) read a lot better and makes more sense. :)

Was going to test the patch but apparently my MAMP's PHP is too old to run D8 so maybe later!

AaronBauman’s picture

Status: Needs review » Needs work

So now, instead of using the technically correct and accurate term "Boolean", we're going to change this to a recursively defined and not necessarily accurate "Yes/No Option"? I think we can assume that admins are smart enough to read the description directly below the word "Boolean" to figure out what it means. If we cannot make that assumption, then why do we have a description in the first place?

I don't argue that "Boolean" is the perfect label, but I do argue that "Yes/No Option" is worse.

superspring’s picture

I think that the term 'Boolean' does need to stay in the name somewhere since programmers and developers will want to know how it's being stored in the database, rather than just an Enum with two fields.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Prashant.c’s picture

Version: 8.1.x-dev » 8.3.x-dev
Issue summary: View changes

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Issue summary: View changes
Status: Needs work » Needs review
Issue tags: +Bug Smash Initiative, +user interface text
quietone’s picture

Title: "Boolean" field type label » Change the label of the Boolean field type from 'Boolean' to 'Yes/No option'

Hopefully, improving the title.

quietone’s picture

Component: file.module » field system

Oops, meant to change the component as well.

quietone’s picture

Issue summary: View changes
FileSize
23.02 KB
36.72 KB
730 bytes

Added a before and after screenshot to the IS.

The attached patch is not a complete reroll, it just has label change for Boolean. The other changes in the patch are slight changes to the wording of the description for the fields that are in the D7 list.module.

quietone’s picture

I meant to add that I asked for feedback on this issue in #ux. benjifisher responded asking for an updated screenshot, which I did in the previous comment. Also, I aborted the tests because I thought that can wait until after there is feedback.

vikashsoni’s picture

FileSize
15.59 KB
14.64 KB

@quietone
patch apply successfully and boolen field label changed

quietone’s picture

@vikashsoni, thanks for your interest in this issue. However, #26 says that is waiting for feedback from the folks in #ux which mean there is nothing to do until that happens. Adding screenshots (which are duplicates of the ones I added about 3 1/2 hours before yours) is not advancing this issue. Therefor removing credit. The contributor guide on Drupal.org has information about the process to Review a patch or merge request.

AaronMcHale’s picture

Issue tags: +Needs usability review

Adding ux review tag, issued queued for review at #3216349: Drupal Usability Meeting 2021-06-11.

benjifisher’s picture

We discussed this issue at #3216349: Drupal Usability Meeting 2021-06-11. There were about 6 people present, with a variety of backgrounds: some who speak English as their first language, some not; front- and back-end developers, site builders, etc.

There was a pretty solid consensus that "Boolean" is the standard, recognized term for this sort of field, and we should leave this form as it is.

Part of the problem with "Yes/No" is that it is only one of several similar alternatives: 0/1, True/False, On/Off. In fact, when you add a Boolean field, you get to the settings page for the field (such as /admin/structure/types/manage/test_content_type/fields/node.test_content_type.field_test_boolean_field) and have a chance to fill in text for the '"On" label' and the '"Off" label'.

One suggestion came up after the meeting to combine the options: "Boolean (Yes/No)" or "Boolean (True/False)". Personally, I do not like that option because parentheses are already used on the same list to describe variants: "Number (decimal)", "Number (float)", and so on.

Our recommendation is to close this issue as "won't fix". I will not do that just yet in case anyone else wants to respond.

quietone’s picture

@benjifisher, thank you for reporting back on the discussion.

AaronMcHale’s picture

Issue tags: -Needs usability review
quietone’s picture

Issue summary: View changes
Status: Needs review » Closed (won't fix)

It has been just over a fortnight since the Usability review recommended that this should be closed as won't fix. It is always hard to know how long to wait but this has had little interest and those that commented did not agree. I think it is time.

Therefor closing as won't fix.