Fix edited timestamp updated when transforming / resolving comments
What does this MR do?
This MR fixes edited timestamp updated when transforming / resolving comments without data migration.
Closes #27311 (closed)
Migrations
rake db:migrate
WARNING: This version of GitLab depends on gitlab-shell 13.17.0, but you're running 13.15.0. Please update gitlab-shell.
== 20210303053341 AddLastEditedAtAndLastEditedByIdToNotes: migrating ==========
-- add_column(:notes, :last_edited_at, :datetime_with_timezone)
-> 0.0029s
== 20210303053341 AddLastEditedAtAndLastEditedByIdToNotes: migrated (0.0030s) =
rake db:rollback
WARNING: This version of GitLab depends on gitlab-shell 13.17.0, but you're running 13.15.0. Please update gitlab-shell.
== 20210303053341 AddLastEditedAtAndLastEditedByIdToNotes: reverting ==========
-- remove_column(:notes, :last_edited_at, :datetime_with_timezone)
-> 0.0040s
== 20210303053341 AddLastEditedAtAndLastEditedByIdToNotes: reverted (0.0060s) =
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Mycroft Kang