Improve settings pages design by prioritizing content: Conditional features follow-up
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Follow-up of https://gitlab.com/gitlab-org/gitlab-ce/issues/49738
In https://gitlab.com/gitlab-org/gitlab-ce/issues/49738 we work towards improving the project settings page. We have previously improved the group settings page in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21115.
There are a few sections that may have been missed in each case due to feature availability or general state conditions. This is mainly EE (feature availability) but CE should also be checked for conditional partials.
This has been highlighted in https://gitlab.com/gitlab-org/gitlab-ce/issues/49738#note_150661255 where we have "Repository size limit" and "Classification label" in the general settings panel (top panel).
When https://gitlab.com/gitlab-org/gitlab-ce/issues/49738 is closed, eng should provide ux with a branch or 1:1 to work through the leftover cases that aren't so easy to reveal and highlight these in the issue or temp MR.