View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 6
IDProjectCategoryView StatusDate SubmittedLast Update
18134Bug reportsSurvey editingpublic2022-05-19 18:212022-06-22 14:58
Reporterritapas Assigned To 
PrioritynormalSeveritypartial_block 
Status confirmedResolutionopen 
Product Version3.28.x 
Summary18134: Present subquestions/answer options in random order has no clue about current state
Description

in the Survey menu - list questions window you can mass change question parameters.
The "Present subquestions/answer options in random order" always shows the state as OFF even when it's ON. Is that done on purpose?

Steps To Reproduce

Steps to reproduce

Create survey with at least 2 question groups with at least 2 questions inside. One of those must have "Present subquestions/answer options in random order" to ON (this applies for instance for List (radio) type.
Go to Settings-Survey menu-  List questions.
Select one question at least, then in the drowpdown choose "Present subquestions/answer options in random order"

Expected result

I expect to be shown the current "Present subquestions/answer options in random order" state

Actual result

The Set "Present subquestions/answer options in random order" state always shows the "Present subquestions/answer options in random order" state as OFF even when it's ON.

this also happens in limesurvey paas, v. 3.28.11

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)3.28.8 (build 220426)
I will donate to the project if issue is resolvedNo
BrowserMozilla Firefox
Database type & versionphp-mysql-5.4.16
Server OS (if known)Red Hat Enterprise Linux Server release 7.5 (Maipo)
Webserver software & version (if known)httpd-2.4.6-80
PHP Versionrh-php71

Users monitoring this issue

User List ritapas

Activities

ritapas

ritapas

2022-06-09 13:34

reporter   ~70314

still present in 3.28.13 but however the setting is applied as expected
gabrieljenik

gabrieljenik

2022-06-14 23:10

manager   ~70364

Will try to reproduce it

Issue History

Date Modified Username Field Change
2022-05-19 18:21 ritapas New Issue
2022-05-19 18:21 ritapas Issue generated from: 18133
2022-05-20 15:54 gabrieljenik Priority none => normal
2022-05-20 15:54 gabrieljenik Severity trivial => partial_block
2022-06-09 13:34 ritapas Note Added: 70314
2022-06-09 13:34 ritapas Bug heat 0 => 2
2022-06-14 23:10 gabrieljenik Assigned To => gabrieljenik
2022-06-14 23:10 gabrieljenik Status new => acknowledged
2022-06-14 23:10 gabrieljenik Note Added: 70364
2022-06-14 23:10 gabrieljenik Bug heat 2 => 4
2022-06-16 18:08 gabrieljenik Assigned To gabrieljenik =>
2022-06-16 18:08 gabrieljenik Status acknowledged => confirmed
2022-06-22 14:58 ritapas Issue Monitored: ritapas
2022-06-22 14:58 ritapas Bug heat 4 => 6