Users shouldn't be locked into default settings that were only default at the time of user creation
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
(We're an EE customer on 10.3.6-ee gitlab-ee@45d0f746bffbb52916c1d1069fe781e71e3fe1bb and in coordination with @teemo are filing some more general issues we've encountered with Gitlab in addition to our more specific issues. These are not specific "this thing is broken" issues, but more general architecture issues with potentially open-ended solutions).
The default Gitlab project limit is 10, we've since raised it to 100, but users created back when it was 10 still retain the 10 setting, simply because it was the default.
This makes it hard to centrally manage Gitlab, you end up having to write your own custom loop-over-every-user-and-set-stuff scripts to correct these, least you have N number of default settings on users purely based on when they created their profile.
Gitlab should make a distinction between a setting that's a default, and something that really has been set specifically for a given user. When global settings are changed users should start using the new default settings, unless that user has specifically been adjusted differently.