View Issue Details

This bug affects 1 person(s).
IDProjectCategoryView StatusLast Update
14467Bug reportsDocumentationpublic2021-02-09 13:44
ReporterDenisChenu Assigned To 
Status acknowledgedResolutionopen 
Product Version3.15.x 
Summary14467: EM : relevance not being recalculated after conditions updated if question are shown before
DescriptionWhen a relevance update a question : if order is OK : it's good. But with a different order : it can be bad

With 3 question , in order Q1, Q2,Q3
If Q3 have a condition on Q2
Q1 have a condition on Q3

If Q1 are shown , it still shown even if Q3 is hidden by relevance
Steps To ReproduceImport included LSS and test
Additional InformationThis is related to 14465
But i think it muts be a Won't fix , because :
1. It's hard to fix …
2. I already trying triggering event after relevance update : javascript loop or very long …
3. It's seems logic than relevance get only previusly seen question
4. It can be easily fixed adding the relevance function of Q3 to Q1.

BUT maybe : you think it must be fixed (i have no idea currently)
And more : i think this must be documented somewhere at manual.
TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)3.15.8 github
I will donate to the project if issue is resolvedNo
Browsernot relevant
Database type & versionnot relevant
Server OS (if known)not relevant
Webserver software & version (if known)not relevant
PHP Versionnot relevant


related to 14955 testingDenisChenu Question relevance is not reassessed after group is shown 
child of 14465 closedDenisChenu EM relevance not being recalculated after conditions changed (Full survey included) 

Users monitoring this issue

User List There are no users monitoring this issue.




2019-01-30 14:08




2019-01-30 15:01

partner   ~50345

I consider this a WON'T FIX because e.g. at the default condition editor tool, you can't set a condition at question X based on question Y if question Y is shown after question X. The editor only shows previous questions and since survey are always run in proper sequential order, the conditions mentioned above would be invalid.


2019-01-30 17:04

developer   ~50348

OK great :).

I move it to "manual"

@cdorin : you can have a look for manual ?

Issue History

Date Modified Username Field Change
2019-01-30 14:08 DenisChenu New Issue
2019-01-30 14:08 DenisChenu Status new => assigned
2019-01-30 14:08 DenisChenu Assigned To => Mazi
2019-01-30 14:08 DenisChenu File Added: limesurvey_survey_relevanceNotTriggerOtherRelevance.lss
2019-01-30 14:08 DenisChenu File Added: simplescreenrecorder.webm
2019-01-30 14:09 DenisChenu Relationship added child of 14465
2019-01-30 15:01 Mazi Note Added: 50345
2019-01-30 15:01 Mazi Assigned To Mazi => DenisChenu
2019-01-30 17:04 DenisChenu Note Added: 50348
2019-01-30 17:05 DenisChenu Assigned To DenisChenu =>
2019-01-30 17:05 DenisChenu Priority none => low
2019-01-30 17:05 DenisChenu Status assigned => new
2019-01-30 17:05 DenisChenu Category Expression Manager => Documentation
2019-01-30 17:05 DenisChenu Summary EM relevance not being recalculated after conditions updated if question are shown before => EM : relevance not being recalculated after conditions updated if question are shown before
2019-05-30 14:16 DenisChenu Relationship added related to 14955
2019-06-05 15:00 cdorin Assigned To => cdorin
2019-06-05 15:00 cdorin Status new => assigned
2021-02-09 13:44 cdorin Assigned To cdorin =>
2021-02-09 13:44 cdorin Status assigned => acknowledged