Configuring a Custom Issue Tracker Service Template enables it for all projects. No way to change them all
Summary
If an admin edits the 'Custom Issue Tracker' service template (/admin/application_settings/services) and activates that service template, it will add that to all projects in the entire instance and add this Custom Issue Tracker to the left-side menu on all projects. That's not good/expected behavior. What's worse, if the admin then deactivates that Custom Issue Tracker or tries to edit its characteristics, those changes are not propagated to all projects.
Steps to reproduce
I'm on GitLab v11.3.4 (gitlab-ce@30f019dca78bb64bcb8b355a267be006884e6d8f)
Be careful ... this change can impact all projects in a GitLab instance. Menu Item: Admin Area > Service Templates > Custom Issue Tracker Change the name, set some URLs, and then activate the Custom Issue Tracker Check any project on the instance to confirm that the issue tracker is now showing in the lefthand menu Return to the admin area and change the Name, URL, etc. Return to the project > Settings > Integrations > Custom Issue Tracker Confirm that the Name and URL are not updated Disable the Issue tracker in the main admin area Confirm that the issue tracker is not deactivated in individual projects
Example Project
I don't have admin access to do this on the main GitLab instance.
What is the current bug behavior?
Custom Issue tracker is automatically enabled for all projects Changes to the settings from the Admin do not propagate to all projects Disabling the custom issue tracker does not propagate to all projects
What is the expected correct behavior?
Activating the service template by the admin should not automatically enable it for all projects Deactivating it centrally, or editing its URL, etc. should propagate the changes to all projects Individual projects should ideally be able to override the centrally configured values
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(I don't have access to get this server-level information)
Results of GitLab application Check
Expand for output related to the GitLab application check
(I don't have access to get this server-level information)