View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 20818 | Bug reports | Question editor | public | 2026-11-04 23:06 | 2026-11-04 23:09 |
| Reporter | c_schmitz | Assigned To | |||
| Priority | normal | Severity | partial_block | ||
| Status | new | Resolution | open | ||
| Summary | 20818: Mandatory means different things per question type and can conflict with the minimum/maximum answers settings | ||||
| Description | This has been confusing survey authors for years. Since 2019 the same kind of report keeps coming back: a mandatory question can't be completed, or the minimum/maximum answers setting seems to be ignored (15363 in 2019, 17330 in 2021, 20622 in 2026). Each time only the reported case was patched, and only for ranking. The underlying inconsistency was never addressed, so every other question type with more than one answer still has the same problem. The "Mandatory" setting is one On/Soft/Off switch, but what it requires depends on the question type, and the question editor doesn't show which rule applies:
The "Minimum answers" and "Maximum answers" settings work separately from mandatory, which causes three problems:
| ||||
| Additional Information | How to finally fix it Another special case for one more question type would only move the confusion elsewhere. We should fix the model itself, once, for all question types with more than one answer field: the question editor should say exactly what "mandatory" requires, and the settings should not be able to contradict each other. Keep the Mandatory switch. For question types with more than one answer field, add a "Required answers" setting next to it:
Mandatory decides whether the question has to be answered at all. "Required answers" decides how much of it. On a question that isn't mandatory, the range only applies once the participant has answered something. Results:
Until this is in place, the question editor should at least warn when a contradictory combination is configured, so authors stop running into it unnoticed. | ||||
| Tags | No tags attached. | ||||
| Bug heat | 0 | ||||
| Complete LimeSurvey version number (& build) | 7.9.1 (master) | ||||
| I will donate to the project if issue is resolved | No | ||||
| Browser | - | ||||
| Database type & version | - | ||||
| Server OS (if known) | - | ||||
| Webserver software & version (if known) | - | ||||
| PHP Version | - | ||||
| Git branch / Pull Request URL | |||||