Date format breaks issue creation

Summary

If JIRA is set to use the following date picker format and user enter the invalid date, JIRA creates issue with broken state and Indexing error will thrown. The date format which can be used to replicate this problem is:

jira.date.picker.java.format=dd.MM.yyyy
jira.date.picker.javascript.format=%d.%m.%Y
jira.date.time.picker.java.format=dd.MM.yyyy HH:mm
jira.date.time.picker.javascript.format=%d.%m.%Y %H:%M

Steps to reproduce:

1. Create a custom field "Date Picker" type and associate it with any create issue screen.
2. Set the date picker format to the format provided above.
3. Create any issue and in the Date Picker field, enter value like "19.04.17" instead of "19.04.2017".
4. Following error will be shown:

   We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persists, contact your administrator as they'll be able to access more specific information in the log file.

1. Open System -> Support Tools -> Instance Health and we'll see Indexing related problem highlighted.
2. Problem can only be replicated in MS SQL based instance

Environment

JIRA 7.3.2 & JIRA 7.3.4

Expected Results

JIRA rejects the issue creation because of the invalid date format.

Actual Results

JIRA created an issue in broken state. Checking from database using the following query will show the issue created without any status:

SELECT jiraissue.id issue_id, jiraissue.workflow_id, os_wfentry.*  FROM jiraissue JOIN os_wfentry ON jiraissue.workflow_id = os_wfentry.id
WHERE jiraissue.issuenum = <issue-number> AND (os_wfentry.state IS NULL OR os_wfentry.state = 0);

Workaround

Using different date picker format could help with this problem. Tested with default date picker format provided in JIRA (d/MMM/yy) and the issue not reproducible.