View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|16157||Bug reports||Other||public||2020-04-20 10:36||2020-11-27 10:05|
|Summary||16157: multiple choice option "other" cannot be selected without entering a text|
When using question type "multiple choice" with the general question setting "other", you cannot just select the checkbox for other. The checkbox is only ticked if you enter a text in the text field. The current implementation might lead to a systematic underestimation of the other category.
I must be possible to check the checkbox "other" without entering a text.
|Tags||No tags attached.|
|Complete LimeSurvey version number (& build)||4.1.18|
|I will donate to the project if issue is resolved||No|
|Sync to Zoho Project||Yes|
|Database & DB-Version||n/a|
|Server OS (if known)|
|Webserver software & version (if known)|
The implementation of "other" with single choice and dropdown is working as it should.
Very old issue : wok like this since 1.81 and maybe before.
Then : more a feature than a bug.
Yes, I know that this is an old one, but nevertheless something that really wrong (I use the word wrong only in rare cases - but this is really wrong, wrong, wrong).
Would this affect the way in which data is currently collected by LS users? I see Frederik's point and I agree to it (from a methodological perspective)
In mine template (since SkeletonQuest) : i hide the opther checkbox since it was not a real checkbox.
And there are nbo checkbox (for other) in Multiple choice with comment : https://demo.sondages.me/47483?lang=fr#
There is currently no datafield in LimeSurvey to store the state of the select box.
This is a major issue for me as well. I have identified that this is the primary cause of people dropping out of surveys (as they think they can't choose other when the checkbox doesn't tick). It is also certainly resulting in under-reporting of other. I need respondents to be able to choose other without entering text if they don't want to.
This has a flow-on effect that when exporting to SPSS you need to generate a variable for other to run multiple response tables. This can be done with a syntax, but it is added time and complication.
@tixeon : can you try with
in your custom.css and see if it's better
I agree that this makes no sense, what so ever. Even if it was always like this, this doesn't make it right.
I think we need to allow people to tick "other" and then the survey admin must be able to decide if the text box for other should be mandatory or not.
I don't think the way it currently is, is a good solution, especially as it usually works differently in other survey tools. "Other" should always be just a normal answer option, because usually we need to include it also into analysis. So I am not sure why some one thought it would be a good idea to not treat it like a normal answer option.
But while we are at it and have to fix the database structure anyway: Why not make it really right and flexible? I think we should have the possibility to put a text field for any of the answers. Currently this is done via workarounds by hiding text boxes from a mutliple with comments. We could actually get rid of this whole question type if we offer the option to show a comment box to any of the answer options / subquestions and the survey creator decides by ticking a check box for which of the answeroptions / subquestions they want to show an additional text box and if it should be mandatory to fill the text box, if the option was chosen.
I agree that being able to append a free text box to any subquestion (answer option) is needed to ensure Limesurvey keeps up with other survey applications. I have an account with another online survey tool that I use if a survey requires free text boxes on 2 or more (but not all) answer options because the work-around in limesurvey is too annoying for questionnaires with lots of questions of this type (and I can't always get it to work).
The change is quite big as underlined by Carsten earlier. Smth to be discussed later (for LS5)
|2020-04-20 10:36||f_funke||New Issue|
|2020-04-20 10:36||f_funke||Status||new => assigned|
|2020-04-20 10:36||f_funke||Assigned To||=> cdorin|
|2020-04-20 10:40||f_funke||Note Added: 57259|
|2020-04-20 11:02||f_funke||Relationship added||related to 16158|
|2020-04-20 11:28||DenisChenu||Note Added: 57261|
|2020-04-20 11:42||f_funke||Relationship added||related to 16159|
|2020-04-20 11:48||f_funke||Note Added: 57263|
|2020-04-20 11:48||f_funke||Note Added: 57264|
|2020-07-09 16:53||cdorin||Assigned To||cdorin =>|
|2020-07-09 16:53||cdorin||Priority||none => low|
|2020-07-09 16:53||cdorin||Status||assigned => feedback|
|2020-07-09 16:53||cdorin||Note Added: 58871|
|2020-07-09 17:38||DenisChenu||Note Added: 58878|
|2020-11-17 15:58||c_schmitz||Note Added: 60679|
|2020-11-17 22:52||tixeon||Note Added: 60685|
|2020-11-18 08:14||DenisChenu||Note Added: 60687|
|2020-11-18 08:14||DenisChenu||File Added: Capture d’écran du 2020-11-18 08-14-10.png|
|2020-11-25 14:09||holch||Note Added: 60756|
|2020-11-26 00:45||tixeon||Note Added: 60759|
|2020-11-27 10:05||cdorin||Status||feedback => acknowledged|
|2020-11-27 10:05||cdorin||Target Version||=> 5.0.0dev|
|2020-11-27 10:05||cdorin||Sync to Zoho Project||=> Yes|
|2020-11-27 10:05||cdorin||Note Added: 60774|