-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Affects Version/s: 11.2.0
-
Component/s: Assets - Object, Type and Schema
-
Severity 3 - Minor
Issue Summary
Datetime custom field value placeholder in assets custom field AQL does not match any assets when using Jira datetime picker placeholder values
Steps to Reproduce
- Create a new empty assets object schema called 'test' and assets object type called 'testobject', which includes a new attribute of type datetime
- Create two objects with two unique datetimes


- Create a new project
- Create a date time picker custom field

- Create an assets object custom field and configure it to query 'testobject' assets objects based on matching 'test-datetime' datetime values from the above date time picker




- In your new project, add your new assets custom field and date time picker as fields on the default issue screen

- Use the Jira issue 'create' button, to begin creating a new issue and configure the 'test datetime picker' 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 'test datetime picker' 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:
| Testing Requirements | Version | Affected Version |
|---|---|---|
| Customers Reported Version | 11.2.0 | Yes |
| Most Recent Bug-Fix Release | ||
| Previous Major Release | ||
| Most Recent LTS | 11.3.0 | No |
| Previous Supported LTS | 10.3.13 | No |
| Previous Supported LTS | 5.12.29 | No |
| Other Versions.. | ||
| (Add rows as needed) |
- links to
- mentioned in
-
Page Loading...