View Issue Details

This bug affects 1 person(s).
 2
IDProjectCategoryView StatusLast Update
07424Feature requestsSurvey editingpublic2021-11-11 16:20
Reporteruser9124Assigned Togalads  
PrioritynormalSeverityfeature 
Status acknowledgedResolutionopen 
Summary07424: Multiple question types in array
Description

There is a work a workaround for this but it is hideously complex and a dead end for non-programmers.

http://docs.limesurvey.org/tiki-index.php?page=Workarounds:+Question+design,+layout+and+templating#Multiple_question_types_in_array

This type of question is critical for many of our research surveys and invalidates LimeSurvey as an option.

Implementation of the workaround in a user friendly fashion would place LimeSurvey as one of the very few online survey systems that offer this feature (only one survey system out of just over twenty investigated so far).

Additional Information

A possible solution: Positional information in each question
SurveyMonkey has positional information for each question to wit:
Place on new row (default)
Place on same row as previous question

Additionally you would require line height options, display heading, display row labels, and possibly column width. (thinking arrays next to each other as well as single fields)

The downside to this is the tab order is column based; a small price to pay to allow this feature.

TagsNo tags attached.
Bug heat2
Story point estimate
Users affected %

Users monitoring this issue

There are no users monitoring this issue.

Activities

user1

2010-08-05 03:34

  ~24354

As you said, the workaround is very complex for non programmers.
It's also the reason we can't use LS in our projects.

I was trying to suggest something like this here:

http://ideas.limesurvey.org/ideatorrent/idea/171/

Issue History

Date Modified Username Field Change
2019-11-01 17:25 c_schmitz Category Survey design => Survey editing
2021-11-11 16:20 galads Assigned To => galads
2021-11-11 16:20 galads Status acknowledged => confirmed
2021-11-11 16:20 galads Status confirmed => acknowledged