Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #8061

Closed
Open
Created Oct 17, 2014 by Administrator@rootOwner

Unable to change project visibility as admin if any restrictions are set in the config.

Created by: dreis2211

Hey,

we experience the problem, that our admins can't change the visibility of projects anymore. We have restricted our users to only create internal projects. Admins should be still able to change those settings, though.

I think this was introduced with the following change 4967c087

The validation on the database row shouldn't check against the config settings in my opinion. As the config setting states, the restricted_visibility_levels should only apply for non-admin users and therefore such a "low-level" check is not appropriate.

Cheers

Assignee
Assign to
Time tracking