View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 07145 | Feature requests | Accessibility | public | 2013-01-06 01:41 | 2021-03-08 20:08 |
| Reporter | mfaber | Assigned To | mfaber | ||
| Priority | normal | Severity | feature | ||
| Status | closed | Resolution | fixed | ||
| Product Version | 2.05+ | ||||
| Fixed in Version | 2.05+ | ||||
| Summary | 07145: Validation criteria fields missing for question type date&time | ||||
| Description | At the moment I do not see an easy way to validate an answer to a date question. | ||||
| Steps To Reproduce | choose any inactive survey | ||||
| Additional Information | There's a workaround in the wiki...involving javascript, however | ||||
| Tags | No tags attached. | ||||
| Bug heat | 6 | ||||
| Git branch / Pull Request URL | |||||
|
Sorry to bug you guys. Are there plans to implement a validation field or minimum maximum fields for the date/time question type anytime soon? I really hope for 2.1... We are extensively working with dates and at the moment I just do not see an easy way to prevent "nonsense" entries. We often need to check whether a date asked in one question comes e.g. 1-30 days after a date entered in a previous question but the validation field to do this is missing in the date/time question... |
|
|
see pull request for 2.05 (validation field) |
|
|
Fix committed to 2.05 branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=13073 |
|
|
LimeSurvey: 2.05 81fa4b54 2013-09-25 22:42 Details Diff |
Merge pull request #93 from mfaber/validate2 New feature 07145: validation field for date/time question |
Affected Issues 07145 |
|
| mod - application/helpers/common_helper.php | Diff File | ||
| mod - application/helpers/expressions/em_manager_helper.php | Diff File | ||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-01-06 01:41 | mfaber | New Issue | |
| 2013-01-06 01:41 | mfaber | Issue Monitored: mfaber | |
| 2013-01-21 09:20 | mfaber | Issue End Monitor: mfaber | |
| 2013-01-21 09:20 | mfaber | Issue Monitored: mfaber | |
| 2013-03-15 12:46 | danielschmitteurac | Issue Monitored: danielschmitteurac | |
| 2013-03-17 15:55 | c_schmitz | Project | @10@ => Feature requests |
| 2013-03-17 15:55 | c_schmitz | Category | Survey Design => Other issues |
| 2013-03-17 15:55 | c_schmitz | Severity | @50@ => feature |
| 2013-03-17 15:55 | c_schmitz | Status | new => acknowledged |
| 2013-03-17 15:55 | c_schmitz | Category | Other issues => Accessibility |
| 2013-04-26 16:00 | mfaber | Note Added: 25141 | |
| 2013-07-09 11:12 | mfaber | Assigned To | => mfaber |
| 2013-07-09 11:12 | mfaber | Status | acknowledged => assigned |
| 2013-07-09 11:14 | mfaber | Note Added: 25745 | |
| 2013-07-14 00:24 | mfaber | Product Version | => 2.05+ |
| 2013-07-14 00:24 | mfaber | Fixed in Version | => 2.05+ |
| 2013-07-14 00:24 | mfaber | Note Edited: 25745 | |
| 2013-07-25 03:56 | mfaber | Resolution | open => fixed |
| 2013-09-25 22:48 | mfaber | Changeset attached | => LimeSurvey 2.05 81fa4b54 |
| 2013-09-25 22:59 | mfaber | Note Added: 26371 | |
| 2013-09-25 22:59 | mfaber | Status | assigned => resolved |
| 2014-01-11 09:04 | mfaber | Status | resolved => closed |
| 2021-08-02 18:52 | guest | Bug heat | 2 => 6 |