Service Templates should not be visible/available when the corresponding project settings are not available

Problem to solve

GitLab provides the global service templates configuration for defaults for projects which are configured in projects integration settings. However, not all services are always available.

For example, the Jenkins CI service integration is not available in the Core (free) tier, but only in higher, paid tiers.

The service template being available in the global configuration but then not in projects settings is pretty confusing.

Having a global configuration for defaults for something that is not usable seems useless, cluttered and misleading.

Intended users

GitLab Administrator Users

Further details

Proposal

Service templates should not be available when their corresponding instance configuration is not available either.

Permissions and Security

No

Documentation

The Service templates documentation will have to be updated.

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Core

Links / references

Edited Sep 02, 2020 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading