-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
This isn't a bug. The createdOn parameter isn't very useful as the database often saves dates with milliseconds precision.
Task:
- Add note about that to the docs
====
How to reproduce:
- Have a task with a creation date, e.g. 2015-05-18T10:36:17
- Make a REST call GET /task?created=2015-05-18T10:36:17
Expected:
- Response contains task
Observed:
- Response is empty array
Hint: Same problem exists when using the POST variant (using createdOn, see CAM-3900)