Default projects limit setting sticks to users on creation and cannot be changed globally later
A friend was setting up GitLab for a company and set up a default projects limit of 0 thinking this would remove the limit to be infinite. Well that didn't work and the new normal user account he made couldn't make any projects. So he set the projects limit to a really high number instead, like 1000. Even after saving, restarting, and reconfiguring it didn't change the test user account he made.
What we quickly figured out was that the default limit setting at the user's creation stuck to the user's account.
I realize that accounts have their own projects limit settings attached, but I think that:
- When an account is set to the global default, it should automatically change to whatever the global default changes to at a later time.
- Accounts that have custom values shouldn't be affected by the global value changes by default
- There should however be an option added to force a new global value to all accounts even with custom values
- The ability to remove projects limit to be infinite. Perhaps with a value of -1 to indicate infinite.
I think this will be a useful option for GitLab admins managing very large user base instances and EE admins handling more specific and varying user permissions, especially at large scale.