Update docs for 17.8 upgrades
What does this MR do and why?
Alert users of a possible error that might
come up when upgrading to 17.8 related to
default work item types created in the
work_item_types table.
A user reported the documented problem in #423483 (comment 2385606585) and we had another one through customer support. We are not backporting a fix as we only do bug backports for the current stable release (17.9 at the time of writing). And since 17.8 is a required stop, backporting to 17.9 won't help as everyone has to run the migration in 17.8.
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Merge request reports
Activity
assigned to @mcelicalderonG
@msedlakjakubowski could you please review this doc only change?
requested review from @msedlakjakubowski
added groupproject management label
added devopsplan sectiondev labels
added documentation label
1 Message 📖 This merge request adds or changes documentation files and requires Technical Writing review. The review should happen before merge, but can be post-merge if the merge request is time sensitive. Documentation review
The following files require a review from a technical writer:
-
doc/update/versions/gitlab_17_changes.md(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.mdfiles that you've changed. The first few lines of each*.mdfile identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
🔁 danger-reviewjob that generated this comment.Generated by
🚫 DangerEdited by ****-
Resolved by 🤖 GitLab Bot 🤖Proper labels assigned to this merge request. Please ignore me.
👋 @mcelicalderonG- please see the following guidance and update this merge request.1 Error ❌ Please add typebug typefeature, or typemaintenance label to this merge request. Edited by 🤖 GitLab Bot 🤖
added docs-only label
-
@mcelicalderonG Added some tweaks and it now looks good
👍 Thank you, @msedlakjakubowski!
changed milestone to %17.10
started a merge train
