View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
15154Bug reportsImport/Exportpublic2019-08-12 14:262021-09-09 08:50
Reporterdavebostockgmail Assigned Togalads  
PrioritynoneSeveritypartial_block 
Status closedResolutionfixed 
Product Version3.17.x 
Summary15154: Export of data incorrect when an Exclusive is in consistent in a Multiple Choice Question
Description

When an exclusive option is added to a multiple choice question the data is stored inconsistently when compared to other answer options this affects the export and reporting of the data and is not in line with other research software conventions.

The data in a multiple choice question is either Y or N for selected answer or Not ...and this is exported as a 1 or a 0 in the data set allowing you to get a base to calculate the correct %'s needed, when you apply an Exclusive option then instead of being N the other answers are shown as N/A which leaves the exported data blank.

This is an issue if the questions has logic to display it or not ... as you cannot then tell if the sub question (answer option) was seen and not answered or not seen due to filtering.

Steps To Reproduce

Create a survey with a multiple choice question
Make one of the answers exclusive
Run through the survey several times
Export the data to see the incorrect export when compared to the other answers.

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)3.17.7+190627
I will donate to the project if issue is resolvedNo
BrowserChrome
Database type & versionMySQL 5.x
Server OS (if known)Ubuntu 16
Webserver software & version (if known)Apache 2
PHP VersionPHP 5.6

Users monitoring this issue

There are no users monitoring this issue.

Activities

ollehar

ollehar

2021-03-10 22:24

administrator   ~63191

Please update to the latest version and check if the bug can still be reproduced. Thank you.
galads

galads

2021-09-09 08:50

reporter   ~66416

Hello davebostockgmail,
I checked this with the latest version and could not reproduce, so this is most likely fixed for good.
Therefore, I am closing this issue. If you still can reproduce the issue using the latest version, please feel free to re-open the issue.
Thank you!

galads

Issue History

Date Modified Username Field Change
2019-08-12 14:26 davebostockgmail New Issue
2019-12-03 15:53 cdorin Assigned To => cdorin
2019-12-03 15:53 cdorin Status new => assigned
2021-02-08 13:02 cdorin Assigned To cdorin =>
2021-02-08 13:02 cdorin Status assigned => acknowledged
2021-03-10 22:24 ollehar Status acknowledged => feedback
2021-03-10 22:24 ollehar Note Added: 63191
2021-09-09 08:50 galads Assigned To => galads
2021-09-09 08:50 galads Status feedback => closed
2021-09-09 08:50 galads Resolution open => fixed
2021-09-09 08:50 galads Note Added: 66416
2021-09-09 08:50 galads Bug heat 2 => 4