Incorrect timeformats for created_at and closed_at fields using the API for anlyze issues
I'm working with GitLab issues, and pulling those issues through API to measure the number of hours it takes to close an issue.
Doing that i found, that for the closed_at field from API has a timedate before the created_at field.
This is derived from the closed_at field not having the same timeformat (timezone difference) as the created_at field has.
Using GitLab Community Edition 12.1.6
What is the current bug behavior?
Examples, from getting info for issues using the API:
What is the expected correct behavior?
There should be used the same date/timestamp for the created_at and closed_at field.