Defect #19354
closedUnexpected milliseconds in JSON time attributes
0%
Description
our original request #5901 was about exposing Redmine version through REST API so that clients would know what functionality is supported by the server.
that request is still relevant, but I decided to submit a smaller feature request about date formats.
Redmine 3.x broke backward compatibility - the date format used in REST responses is different from Redmine 2.6:
From redmine 2.6.0: "updated_on":"2015-01-23T00:15:24Z"
From redmine 3.0.0: "updated_on":"2015-01-29T10:06:19.000Z"
one of our users submitted this bug report: https://github.com/taskadapter/redmine-java-api/pull/175
if we could query Redmine to see its version, we could pick the right date format instead of guessing... now we will have to check "are there 3 more digits after this and before that?"..
but a better option would be querying Redmine to see what date format it uses for long dates and short dates - because this is what the library actually cares about.