Issue Summary

v11.3.4-11.3.8

When an Assets custom Date (or Date/Time) attribute is filtered with AQL comparison operators (=, <, >, <=, >=, or a range), the query returns incorrect results — no objects for equality/less-than/range queries, and all objects for greater-than queries — whenever the Jira Look & Feel "Complete Date/Time Format" is configured with a 2-digit year (e.g. dd/MMM/yy).

Steps to Reproduce

1. In Admin → System → Look and Feel, set the Complete Date/Time Format to a 2-digit-year pattern, e.g. dd/MMM/yy h:mm a.
2. Create an Assets object type (e.g. Month) with a custom Date attribute named Start.
3. Create objects with these Start values: 2026-06-01, 2026-07-01, 2026-08-01.
4. Run this AQL query (Assets → object search or IQL):

objectType = Month AND "Period Start" >= "2026-06-22" AND "Period Start" <= "2026-07-25"

Expected Results

1 object

Actual Results

0 objects

Workaround

Use a 4-digit-year Look & Feel format (yyyy)

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: