UX for Group-Level integration settings MVC
As part of the mass-integration epic, as a follow up to the instance-level integration sub-epic, we want to implement an MVC for group-level integration settings.
As described in the mass-integration epic, the key feature for this MVC is:
Project-level integrations now inherit Group-level integration values by default This inherited integration is a one-to-many relationship. When a group-level integration is created, all projects within that group immediately inherit that integration (unless otherwise configured). When a change is made to the group-level integration, that change is reflected directly in each of the projects.
There are some additional items we need to consider:
- For this MVC, should we implement for sub-groups or only one parent group? If we want to implement for one group, should that be a project's top-level parent or direct parent (if the project is nested more than one level).
- Will the menu item and integration settings views resemble those of instance and project level? Are there any special considerations we need to make in the UI at the group level?
- What does the interaction look like for overriding instance-level settings at the group level? Is it assumed an active group level integration automatically overrides the instance-level setting by default? Is it implied that updating fields override the instance-level setting? Or does the user need to explicitly toggle the override on/off?
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.