View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|08300||Feature requests||Survey taking||public||2013-10-19 11:57||2021-11-25 10:14|
|Summary||08300: Group complete index show group without testing relevance (and other think)|
|Description||If you set group relevance to 0 : group are shown in index if maxstep<step.|
|Steps To Reproduce||Import included survey and test (after look at relevance)|
|Additional Information||Think we must have different otion here:|
- Show complete group but "don't activate" click if maxstep>step)
- Show or hide not relevant group (with all quetsion not relevant or group not relevant)
There are some issue too with "mandatory question" : user click on last group: but are push to last mandatory question.
|Tags||No tags attached.|
limesurvey_survey_index.lss (16,767 bytes)
The first is easy : can do it.
Second one is more tricky
EM can send :
- if group is relevant or not (with question too)
- If group as some badly answered question
- Group index option can have
- with/without relevant index
- Unclickable group depend on maxtstep
- Unclickable question depend on last "ALl OK" group
TODO: think same for question (but question are todo actually)
@c_schmitz & @sammousa : please : did I add an the 4 options ?
But then did i set it with multi checkbox or only one selector ?
Group relevance can not be applied to the full question index.
Since group relevance might depend on previous filled in questions / groups.
Basically if you want to have a full group index displayed you must not use relevances that cross group boundaries.
Alternatively we could make an exemption for the relevance equation 0 since that's always irrelevant.
I do some test: i think we can have a real jumpTo with "NO DB save" (because actually this one are not used really).
1. save laststeps
3. Look at session group
AFter the session index are filled with all group, stop at first "not validate"
It work, but then i'm sure we can break Server memory because we jump at last page for each user each time.
Hello, I'm having the same problem described here or in 08932, althought in my case, the groups are hidden by a very simple relevance equation based on a prefilled question, by URL; question ubicated in the very first group of the survey.
I am using something like:
In the relevance equation of a group controlled by that question/parameter, the condition included is like:
In 08932, c_schmitz indicated <<Fixing this would mean that all questions needs to be evaluated at all times. This would be way to slow so this is a no-fix. >>. However, as the reporter signaled, perhaps it could be treated as an additional one-time evaluating at the first time the survey loads.
Couldn't be added as a limited, special case of the question index evaluation? Perhaps ignoring (assuming a certain default value) the questions corresponding to step > maxstep. This would also work, I think, with questions prefilled by URL if they belong to an initial group.
Although the logic associated to group's relevance equation could be very complex, the situacions where arises this problem with the full index are probably simpler. If not, we should have used incremental index, isn't it?
Thank very much
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.
Think it's more a misunderstanding :)
The screencast :)
If you set group relevance to 0 : group are shown in index if maxstep < step.
Peek 25-11-2021 09-58.gif (600,782 bytes)
> There are some issue too with "mandatory question" : user click on last group: but are push to last mandatory question.
This one seems OK
|I got it now. Thanks, Denis, I will add it to the backlog|
|Maybe it's more a new feature about index, or a new plugin system.|
|2013-10-19 11:57||DenisChenu||New Issue|
|2013-10-19 11:58||DenisChenu||File Added: limesurvey_survey_index.lss|
|2013-10-19 11:58||DenisChenu||Note Added: 26835|
|2013-10-19 12:37||DenisChenu||Note Edited: 26835||View Revisions|
|2013-10-24 01:35||c_schmitz||Assigned To||=> DenisChenu|
|2013-10-24 01:35||c_schmitz||Status||new => assigned|
|2013-10-24 09:32||DenisChenu||Note Added: 26977|
|2013-11-05 14:17||sammousa||Note Added: 27091|
|2013-11-05 16:09||DenisChenu||Note Added: 27093|
|2013-11-05 16:10||DenisChenu||Note Edited: 27093||View Revisions|
|2013-11-19 14:13||DenisChenu||Project||Bug reports => Feature requests|
|2014-04-16 14:29||DenisChenu||Relationship added||has duplicate 08932|
|2015-11-08 10:49||dprado||Note Added: 33537|
|2016-01-05 13:38||delarammahdaviii||Issue Monitored: delarammahdaviii|
|2016-01-19 07:02||delarammahdaviii||Issue End Monitor: delarammahdaviii|
|2016-01-19 07:02||delarammahdaviii||Issue Monitored: delarammahdaviii|
|2016-05-31 10:33||DenisChenu||Assigned To||DenisChenu =>|
|2016-06-04 14:25||DenisChenu||Status||assigned => new|
|2021-11-25 09:52||galads||Note Added: 67542|
|2021-11-25 09:52||galads||Bug heat||20 => 22|
|2021-11-25 09:53||galads||Assigned To||=> galads|
|2021-11-25 09:53||galads||Status||new => closed|
|2021-11-25 09:53||galads||Resolution||open => fixed|
|2021-11-25 09:59||DenisChenu||Status||closed => feedback|
|2021-11-25 09:59||DenisChenu||Resolution||fixed => reopened|
|2021-11-25 09:59||DenisChenu||Note Added: 67543|
|2021-11-25 09:59||DenisChenu||Note Added: 67544|
|2021-11-25 09:59||DenisChenu||File Added: Peek 25-11-2021 09-58.gif|
|2021-11-25 09:59||DenisChenu||Status||feedback => assigned|
|2021-11-25 10:01||DenisChenu||Note Added: 67545|
|2021-11-25 10:09||galads||Note Added: 67550|
|2021-11-25 10:09||galads||Severity||@50@ => feature|
|2021-11-25 10:09||galads||Product Version||2.05 RC =>|
|2021-11-25 10:14||DenisChenu||Note Added: 67552|