-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
10.3.0, 10.6.0, 10.3.6, 10.3.7, 10.7.0
-
Severity 2 - Major
-
Issue Summary
Assets not supporting time zone correctly in AQL search when running with JDK 21.
This issue probably exist in Assets import, post functions and all areas using date time comparison with zone.
Steps to Reproduce
- run Jira with JDK 21
- create an object schema called Test Schema
- create an object under the schema with one new attribute purchased of Date type
- create an object A under Test Schema with purchased being "14 Aug 2025"
- go to "search for objects"
- first search: type AQL purchased > "2025-03-25 17:30" and search, object A will show
- second search: type AQL purchased > "2025-03-25 17:30 Australia/Melbourne" and search
Expected Results
Object A ** shown in both search
Actual Results
Object A only shown in first search result, not the second one
Workaround
Run Jira with JDK 17
Versions Tested
This issue impacted all Assets version released and support to run with JDK 21, including 10.3.0 and later.
| Testing Requirements | Version | Affected Version |
|---|---|---|
| Customers Reported Version | 10.3.6 | Yes |
| Most Recent Bug-Fix Release | 10.6.1 | Yes |
| Previous Major Release | 10.6.0 | Yes |
| Most Recent LTS | 10.3.6 | Yes |
- links to
- mentioned in
-
Page Failed to load
[JSDSERVER-16235] Assets Date Time issue in JDK 21
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 1023303 ] |
| Labels | New: ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 1023119 ] |
| Description |
Original:
h3. Issue Summary
Assets not supporting JDK 21 when running with JDK 21 h3. Steps to Reproduce # run Jira with *JDK 21* # create an object schema called *Test Schema* # create an object under the schema with one new attribute *purchased* of Date type # create an *object A* under Test Schema with *purchased being "14 Aug 2025"* # *go to "search for objects"* # first search: type AQL *purchased > "2025-03-25 17:30"* and search, object A will show # second search: type AQL *purchased > "2025-03-25 17:30 Australia/Melbourne"* and search h3. Expected Results Object A ** shown in both search h3. Actual Results Object A only shown in first search result, not the second one h3. Workaround Run Jira with JDK 17 h3. Versions Tested This issue impacted all Assets version released and support to run with JDK 21, including 10.3.0 and later. ||Testing Requirements||Version||Affected Version|| |Customers Reported Version|_10.3.6_|_Yes_| |Most Recent Bug-Fix Release|_10.6.1_|_Yes_| |Previous Major Release|10.6.0|_Yes_| |Most Recent LTS|_10.3.6_|_Yes_| This *issue might exist in Assets import, post functions and all areas using date time comparison with zone.* |
New:
h3. Issue Summary
Assets not supporting time zone correctly in *AQL search* when running with JDK 21. This issue probably exist in Assets import, post functions and all areas using date time comparison with zone. h3. Steps to Reproduce # run Jira with *JDK 21* # create an object schema called *Test Schema* # create an object under the schema with one new attribute *purchased* of Date type # create an *object A* under Test Schema with *purchased being "14 Aug 2025"* # *go to "search for objects"* # first search: type AQL *purchased > "2025-03-25 17:30"* and search, object A will show # second search: type AQL *purchased > "2025-03-25 17:30 Australia/Melbourne"* and search h3. Expected Results Object A ** shown in both search h3. Actual Results Object A only shown in first search result, not the second one h3. Workaround Run Jira with JDK 17 h3. Versions Tested This issue impacted all Assets version released and support to run with JDK 21, including 10.3.0 and later. ||Testing Requirements||Version||Affected Version|| |Customers Reported Version|_10.3.6_|_Yes_| |Most Recent Bug-Fix Release|_10.6.1_|_Yes_| |Previous Major Release|10.6.0|_Yes_| |Most Recent LTS|_10.3.6_|_Yes_| |