Details
-
Bug
-
Resolution: Fixed
-
Low
-
6.4.13, 7.1.9
-
6.04
-
Severity 3 - Minor
-
Description
Summary
The problem is similar to JRA-45776 in which the fix has been applied to Due Date but not to Date Picker custom field:
When user edits an issue it's possible to enter an invalid date in a date picker custom field, such as 16/Dec/20016 or 16/Dec/-2016.
Environment
No Look & Feel changes were made, nor were advanced settings for dates configured - everything is left as the default.
Steps to Reproduce
- Create a new Date Picker custom field
- Add the newly created custom field to the appropriate screen.
- Edit or create an issue.
- Populate that field with an invalid result, such as 16/Dec/20016.
Expected Results
JIRA returns a validation error as it does for the Due Date field (see screenshot in JIRA 7.1.9 below)
Actual Results
The date is persisted in the database and JIRA throws following index warnings:
2016-08-08 10:12:53,406 http-nio-8080-exec-20 WARN admin 612x45x1 1va8kry 0:0:0:0:0:0:0:1 /secure/AjaxIssueAction.jspa [c.a.j.i.i.indexers.impl.LocalDateIndexer] Unable to index custom date field 'cusdatepicker(customfield_10200) with value: 20016-12-16 00:00:00.0 2016-08-08 10:12:53,477 http-nio-8080-exec-20 WARN admin 612x45x1 1va8kry 0:0:0:0:0:0:0:1 /secure/AjaxIssueAction.jspa [c.a.j.i.i.indexers.impl.LocalDateIndexer] Unable to index custom date field 'cusdatepicker(customfield_10200) with value: 20016-12-16 00:00:00.0 2016-08-08 10:12:53,615 http-nio-8080-exec-20 WARN admin 612x45x1 1va8kry 0:0:0:0:0:0:0:1 /secure/AjaxIssueAction.jspa [c.a.j.i.i.indexers.impl.LocalDateIndexer] Unable to index custom date field 'cusdatepicker(customfield_10200) with value: 20016-12-16 00:00:00.0
Attachments
Issue Links
- relates to
-
JRASERVER-45776 JIRA does not correctly validate the Date input
- Closed
- was cloned as
-
JRACLOUD-65058 JIRA Cloud does not correctly validate Date input for custom field
- Closed
-
RAID-64 Loading...