Updated autosave.js to save a lock version
requested to merge 34817-issue-description-reverts-to-an-older-version-when-saving-without-prompting-the-conflict into master
What does this MR do?
This is currently ~backstage and the first MR in #34817 (closed). Autosave does not currently account for a description being edited elsewhere, which has caused cases of overwriting updated descriptions. This MR allows us to store the lock_version with the saved description. Next MR will allow us to compare that with the latest.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- [-] 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
Issue #34817 (closed)
Edited by Donald Cook