Admin Area: Add Instance-Level Integration Settings UI
Problem to solve
As part of &2137, we need consistency to configure service integrations.
These are the current views:
| Admin Area: Service Templates | Admin Area: Settings/Integrations |
|---|---|
 |
 |
| Project: Settings/Integrations |
|---|
 |
Further details
Service templates will become service instance-level configuration.
As part of this issue, we have to investigate how to achieve UX consistency and create the appropriate frontend issues.
Proposal
In the admin area, we have to move Service Templates to Settings/Integrations. With this change, we will have consistency when configuring service integration at all levels: instance, group, project.
Currently, there are 4 integrations (Elasticsearch, PlantUML, Third party offers, Snowplow) that are under Settings/Integrations These should be moved under Settings/General for the time being. See comment #196525 (comment 290782591) for more info.
Proposed updates:
| Settings › General | Settings › Integrations |
|---|---|
 |
 |
Summary of updates:
- Move Elasticsearch, PlantUML, Third party offers, Snowplow integrations from Settings › Integrations to Settings › General
- Move table of integration from Service Templates to Settings › Integrations
- Add the Alert component using the
infoclass/styling with a message mentioning the changes. - TBD: Should we add telemetry to the
Go to Settingsbutton on the Alert component as we are planning to do in #202167 (closed)
Copy for Alert component:
**Some settings have moved.**
Elastic search, PlantUML, Snowplow, and third party offers have moved to Settings › General.
[Go to General] [OK, got it]
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.