Mismatching request and response date encoding

[moutend]

This issue is not a backlog4j specific, but I don't know where should I report it, so that I created this issue.

I tried creating an issue with dueDate parameter by using curl command:

curl -X POST "https://xxx.backlog.jp/api/v2/issues?apiKey=xxx&dueDate=2017-08-24T12%3A00%3A00Z&description=test&issueTypeId=xxx&priorityId=3&projectId=xxx&summary=test"

The response was:

{
  "errors": [
    {
      "message": "error.date : dueDate",
      "code": 7,
      "moreInfo": ""
    }
  ]
}

When I call the issues API, the date included in response seems to be encoded by RFC3339, but the 2017-08-24T12:00:00Z is rejected.

I spent a few hours for investigating and I found that the date without T..Z is correct for request parameter.

# Works
curl -X POST "https://xxx.backlog.jp/api/v2/issues?apiKey=xxx&dueDate=2017-08-24&description=test&issueTypeId=xxx&priorityId=3&projectId=xxx&summary=test"

I think this behavior should be documented or fixed.