Issue navigator fails to parse specific date time

Issue Summary

Attempting to search for issues using the JQL updatedDate >= '2019-03-10 02:56' produces an error indicating the date format is invalid. Changing the date or time to anything outside of 2019-03-10 02:00 through 2019-03-10 02:59 successfully returns results.

Steps to Reproduce

1. Perform an advanced search using this JQL in a Jira Cloud site: updatedDate >= '2019-03-10 02:56' or here: https://jira.atlassian.com/issues/?jql=updatedDate%20%3E%3D%20%272019-03-10%2002%3A56%27

Expected Results

The search parses the date successfully and returns results.

Actual Results

An error is returned indicating the date format isn't valid even though it is.

Date value '2019-03-10 02:56' for field 'updatedDate' is invalid. Valid formats include: 'yyyy/MM/dd HH:mm', 'yyyy-MM-dd HH:mm', 'yyyy/MM/dd', 'yyyy-MM-dd', or a period format e.g. '-5d', '4w 2d'.

01:59 on that date works: https://jira.atlassian.com/issues/?jql=updatedDate%20%3E%3D%20%272019-03-10%2001%3A59%27
03:00 on that date also works: https://jira.atlassian.com/issues/?jql=updatedDate%20%3E%3D%20%272019-03-10%2003%3A00%27
Anything in the 02:XX hour on that specific date fails to parse.

The following messages are shown in the Jira logs:

2020-05-15 20:11:12.670	INFO	com.atlassian.jira.datetime.JodaDateTimeFormatter	Pattern "dd/MMM/yy h:mm a" is unable to parse "2019-03-10 02:56": Invalid format: "2019-03-10 02:56" is malformed at "19-03-10 02:56"	 2020-05-15 20:11:12.670	INFO	com.atlassian.jira.datetime.JodaDateTimeFormatter	Pattern "d/MMM/yy" is unable to parse "2019-03-10 02:56": Invalid format: "2019-03-10 02:56" is malformed at "19-03-10 02:56"	 	 
2020-05-15 20:11:12.100	INFO	com.atlassian.jira.issue.search.searchers.transformer.DateSearchInputTransformer.privacy-safe	Unable to parse date '2019-03-10 02:56'.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available