Creating a comment via API can have a created_at date in the past

Summary

When using create issue note/comment API, user able to select whatever date the comment is created. This could create confusion within the thread.

Steps to reproduce

  1. Create an issue in the project
  2. Note the project ID and issue ID
  3. Make the API call `curl --request POST --header "PRIVATE-TOKEN: "
    --url "https://gitlab.example.com/api/v4/projects//issues//notes?body=note" --data "body=yourcommentHERE&created_at=2016-03-11T03:45:40Z"
  4. Observe the comment created on 2016-03-11 even though you're making the API call in 2026.

Example Project

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info 
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.