<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label. For the Community Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug For the Enterprise Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary If i open a merge request and immediately make a comment, the timestamp on the comment will be in the correct timezone, but the opened at time will be UTC. ### Steps to reproduce 1. Create merge request 2. Make a comment 3. Hover over the "Opened ______ by <your name>" timestamp 4. Hover over the timestamp on the comment 5. Notice that the opened at timestamp is after the comment timestamp (in my case by 4 hours currently since I am in America/Detroit timezone) ### Example Project https://gitlab.com/joshfriend/bunnypedia/merge_requests/36 ### What is the current *bug* behavior? MR opened at timestamp:  Commit timestamp pushed soon after opening the MR  ### What is the expected *correct* behavior? The opened at timestamp should be in my current timezone like all the other dates for comments/new commits/etc ### Relevant logs and/or screenshots see above ### Output of checks Reproduced on gitlab.com, see above screenshots and example MR