View Issue Details

IDProjectCategoryView StatusLast Update
15105Feature requests[All Projects] Otherpublic2019-09-19 11:14
Reporterf_funke Assigned Tolime_release_bot  
PrioritynormalSeverityfeature 
Status newResolutionopen 
Product Version4.0.0-RC2 
Target VersionFixed in Version 
Summary15105: "no answer" is preselected
Description

No answer option is preselected but should not be preselected on load.

Steps To Reproduce

just check any question with presentation option "show 'no answer'" = on

TagsNo tags attached.

Activities

cdorin

cdorin

2019-09-18 15:29

manager   ~53629

Isn't this a feature request? just checked now in 2.7x , and it is always preselected. Shall the behaviour be changed?

f_funke

f_funke

2019-09-19 09:00

developer   ~53648

No, from a methodological point of view this is a bug. Because "no answer" implies that a respondent chooses to say "I do not want to answer that question". However, there are many other possibilities why the person did not check any other response (e.g., did overread the question or none of the response options provided is a good answer).

Normally, I am not very strict and try to balance arguments for or against something. But pre-selecting any answer (even if it is "no answer") is really bad survey design. So either LimeSurvey is bad by design - which I doubt - or this is a definitely bug.

DenisChenu

DenisChenu

2019-09-19 09:54

developer   ~53651

@f_funke : Disable «Show no answer» didn't fix the issue ?

In radio list : the «No answer» option is same than an empty text box, or «Please choose …» in a dropdown.

In HTML : a dropdow NEED an empty answer (else the 1st is selected).

f_funke

f_funke

2019-09-19 10:12

developer   ~53652

15104 was a different issue ("no answer" was displayed, even if was set to no in the options).

In a dropdown, the first (and visible) option should always be "select here" (or something like that) and if you want to an additional "no answer". But also in dropdown the first option should never be "no answer" as this implies that no answer is a perfectly fine answer (which it is not because it should only be the very last choice). However, in a select list (technically a HTML dropdown with all response options visible) the "select here" is not necessary.

A more elaborate way of dealing with "no answer" response option would be in combination with madatory questions. On load there are only the substantial response options (e.g., A, B, C). When continuing without choosing an answer respondents are prompted ("Please select an answer.") and the additional response option "no answer" (or additional options like "don't know", "choose not to say", "depends on") is displayed (e.g., A, B, C, no answer). But I guess that relevance equations on the response level would be necessary for that?

DenisChenu

DenisChenu

2019-09-19 10:48

developer   ~53653

Last edited: 2019-09-19 10:50

View 2 revisions

Dropdown non mandatory : 1st seen : «Select answer … », move next, move previous : «No answer» selected

Else : in my opinion : If you need a clean solution : just set your radio list question as mandatory … : no default value, no «No answer» etc …

See https://ux.stackexchange.com/a/76182
See this guideline : https://docs.microsoft.com/fr-fr/windows/win32/uxguide/ctrl-radio-buttons
See the default value part : Have a «Default selectable» option is acceptable … And the exception can be easily managed with mandatory settings.

Else : we can have different look for No answer and answer (see screenshot)



DenisChenu

DenisChenu

2019-09-19 10:53

developer   ~53654

About : dodn't display the 1st time : i'm TOTALLY against this …

Choice : Yes/No/No answer (non mandatory question)
I click on Yes by «inadvertence» (my mouse is doing hers, I have an illness, I am navigating on the keyboard ...)
I NEED a way to check "No Answer" …

cdorin

cdorin

2019-09-19 11:14

manager   ~53655

I talked to @c_schmitz. We will move it (for the moment) to feature requests. There are some other things that need to be dealt with first.

Issue History

Date Modified Username Field Change
2019-08-04 14:35 f_funke New Issue
2019-08-05 15:21 cdorin Assigned To => p_teichmann
2019-08-05 15:21 cdorin Status new => assigned
2019-09-09 10:07 c_schmitz Priority none => urgent
2019-09-09 10:16 c_schmitz Assigned To p_teichmann => lime_release_bot
2019-09-09 10:17 c_schmitz Status assigned => new
2019-09-09 10:42 c_schmitz Tag Attached: sprint
2019-09-18 15:29 cdorin Note Added: 53629
2019-09-19 09:00 f_funke Note Added: 53648
2019-09-19 09:54 DenisChenu Note Added: 53651
2019-09-19 10:12 f_funke Note Added: 53652
2019-09-19 10:48 DenisChenu File Added: Capture d’écran du 2019-09-19 10-46-12.png
2019-09-19 10:48 DenisChenu File Added: Capture d’écran du 2019-09-19 10-46-20.png
2019-09-19 10:48 DenisChenu Note Added: 53653
2019-09-19 10:50 DenisChenu Note Edited: 53653 View Revisions
2019-09-19 10:53 DenisChenu Note Added: 53654
2019-09-19 11:11 cdorin Project Bug reports => Feature requests
2019-09-19 11:11 cdorin Tag Detached: sprint
2019-09-19 11:11 cdorin Priority urgent => normal
2019-09-19 11:11 cdorin Severity @60@ => feature
2019-09-19 11:14 cdorin Note Added: 53655