When I create or update a Milestone using the v3 API, the “Due On” field always defaults to the last 7:00 before the date-time that I specify. For example, if I set “Due On” to “2018-05-14T01:00:00Z”, the value of the field actually ends up being “2018-05-13T07:00:00Z” (so 7:00 the day before). If I set “Due On” to “2018-05-14T08:00:00Z”, the value of the field ends up being “2018-05-14T07:00:00Z” (7:00 earlier that day).
Can someone confirm that this is the expected behaviour? Is there any way to get the field to use the exact date-time value that I entered?