Skip to content

Way to disable Issues globally and for good.

Description

Document enabling and disabling of project-level features in GitLab instance configuration

I know I can uncheck the enable checkbox for issues and set the default for false in the gitlab.rb file, but is there a way that I can effectively eradicate Issues completely from gitlab?  I don't want my users to have any hint that the system even exists.  No icons, no buttons, I don't even want admins to have an enable checkbox in the admin page of a project.  

Is this possible?  The reason being, I already have 3 bug tracking systems in my enterprise to make my life miserable, id be drawn and quartered for even hinting on introducing a fourth.  

If I can't eradicate it, what user account does omnibus use to update the database tables during upgrades?  if it uses gitlab_postgres (or whatever you set it to) I'm toast, but if it uses sys or root for upgrades, then I can remove access to those tables for the gitlab_postgres user.  Id rather the application crash than people activate Issues.

Proposal

It's possible to declare that project-level features be disabled for all new projects on an instance.

This isn't currently documented. Let's add some documentation for it

Links / references

Edited by Mark Fletcher