View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 20488 | Feature requests | Survey taking | public | 2026-04-13 15:40 | 2026-04-14 21:56 |
| Reporter | buhtz | Assigned To | |||
| Priority | none | Severity | feature | ||
| Status | new | Resolution | reopened | ||
| Summary | 20488: Landing page: "This survey includes 10 to 18 questions". | ||||
| Description | Hello,
In translation it would be something like this: "This survey includes 18 questions." If the survey has filters (if clauses) there are not 18 questions for all users. Some of them might see less of 18. The users should know the minimum and maximum number of questions. "This survey includes <min> to <max> questions." As an alternative, if you don't like to expose the <min> value, try this: "This survey includes up to <max> questions." Regards, | ||||
| Additional Information | LS 6.16.2 | ||||
| Tags | No tags attached. | ||||
| Bug heat | 4 | ||||
| Story point estimate | 0 | ||||
| Users affected % | 0 | ||||
|
it's not about not exposing the minimum, it's about the complexity of calculating it. the maximum is a simple query, the minimum would involve evaluating all the possible combinations of interdependent question relevance equations if you're not comfortable with displaying the message to your respondents, you can hide it in the survey settings (settings -> presentation -> there are x questions in this survey) |
|
|
minimum number of questions would be technically challenging and limesurvey has the functionality to hide this message. also, the proposed change to the wording of the message would not work for surveys without relevance equations. |
|
|
Hello mfavetti, I see that it is complex to calculate the minimum. But doesn't such a piece of software exist to do "complex" tasks? The logical consequence would be also to calculate the duration a survey could take. Based on the type and complexity of a question you can calculate the minutes how long it takes to answer that. The methodological literature is full of such numbers. You don't have to re-calculate it every time the survey is modified. Calculate it on-demand via a button/link on the landing page in edit-mode. And calculate it automatically when the survey becomes public. But it is your project and your decision of course. In my understand you also wouldn't accept a PR implementing such a feature? Regards |
|
|
It seems I am also not able to re-close the issue. But I am the reporter. Mantis is quit restrictive. ;) |
|
|
you're welcome to contribute a pr i guess you could look at the minimum as the number of questions with no conditions. beyond that you would need to figure out all the possible combinations of questions that might be displayed and use the combination with the fewest questions. because of how flexible expression manager is, i think this would not be trivial |
|
Than why do you close the issue? Closing signals potential contributors that a PR wouldn't be welcome. I am not that contributor right now. I don't have resources to implement it. And I am also not familiar with the language you are using.
I wouldn't approach the algorithm like this.
Of course not. That is why it need to be implemented, so humans don't need to do it anymore. ;) btw: Mantis becomes annoying. It blocks my posts because I am posting "to much" in a to "short" amount of time. 10 posts in 6 minutes is not spam. I am just active and participating in discussions. Sorry, Mantis. |
|
right, sorry. for some reason in my head was a bug report not feature request. also now that I think about it a bit more, the maximum would also need a similar process. the number shown now is not the maximum, it's the total number of questions which is likely greater than the maximum if there are relevance equations. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-04-13 15:40 | buhtz | New Issue | |
| 2026-04-14 08:26 | mfavetti | Note Added: 84618 | |
| 2026-04-14 08:26 | mfavetti | Bug heat | 0 => 2 |
| 2026-04-14 08:38 | mfavetti | Assigned To | => mfavetti |
| 2026-04-14 08:38 | mfavetti | Status | new => closed |
| 2026-04-14 08:38 | mfavetti | Resolution | open => won't fix |
| 2026-04-14 08:38 | mfavetti | Note Added: 84623 | |
| 2026-04-14 09:01 | buhtz | Status | closed => feedback |
| 2026-04-14 09:01 | buhtz | Resolution | won't fix => reopened |
| 2026-04-14 09:01 | buhtz | Note Added: 84627 | |
| 2026-04-14 09:01 | buhtz | Bug heat | 2 => 4 |
| 2026-04-14 09:02 | buhtz | Note Added: 84628 | |
| 2026-04-14 09:02 | buhtz | Status | feedback => assigned |
| 2026-04-14 09:08 | mfavetti | Note Added: 84630 | |
| 2026-04-14 09:09 | mfavetti | Assigned To | mfavetti => |
| 2026-04-14 09:09 | mfavetti | Assigned To | => mfavetti |
| 2026-04-14 09:09 | mfavetti | Status | assigned => new |
| 2026-04-14 09:09 | mfavetti | Assigned To | mfavetti => |
| 2026-04-14 10:04 | buhtz | Note Added: 84634 | |
| 2026-04-14 21:53 | mfavetti | Category | _ Unknown => Survey taking |
| 2026-04-14 21:54 | mfavetti | Note Added: 84655 | |
| 2026-04-14 21:56 | mfavetti | Note Edited: 84655 |