Issue Summary

Misaligned Look and Feel date ('Day/Month/Year Format') (or datetime - 'Complete Date/Time Format') format and the Jira Java datepicker format (Application Property: jira.date.picker.java.format) (or Jira Java date time picker format - Application Property: jira.date.time.picker.java.format) causes dates / datetimes replaced as part of AQL placeholder replacement to not match any assets (when assets attribute dates / datetimes should match)

Steps to Reproduce

• Adjust the Application property: jira.date.picker.java.format to have a four digit year (note: this is the default in 11.3.0)
• Create a new empty assets object schema called 'test' and assets object type called 'testobject', which includes a new attribute of type datetime (date also causes the same problem)
• Create two objects with two unique datetimes
  
  
• Create a new project
• Create an assets object custom field and configure it to query 'testobject' assets objects based on matching 'duedate' date values from the default 'duedate' custom field

• In your new project, add your new assets custom field as a field on the default issue screen

1. Use the Jira issue 'create' button, to begin creating a new issue and configure the 'duedate' field with a date matching that configured for the 'Test Object 1' assets object you created above

• Open the 'test assets custom field' dropdown, to reveal matching results

Actual Results

No Assets objects are returned matching the 'duedate' value

Expected Results

Assets object ‘Test Object 1’ is returned as an AQL match

Workaround

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

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: