Bug - What's new navigation item re-appearing more frequently then expected.
Summary
The What's new option in the navigation seems to be reappearing for some users, without any additional articles being released to prompt its re-appearance. Please reference this thread for further context.
Steps to reproduce
- Log into GitLab, see
What's New - Click on
What's new - Log out, back in
What is the current bug behavior?
The current behaviour is that for some users the What's new is moving from the Help menu to the nav without any prompt. Occurring in one documented case every 2-3 days.
What is the expected correct behavior?
The expected behaviour is that the What's new menu item will re-appear when new articles have been published at each release (roughly once a month).
Relevant logs and/or screenshots
Output of checks
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.