## Release notes The instance-level GitLab Duo model selection page for GitLab Self-Managed already supports configuring a model for each feature individually. However, **Apply to all** is not shown when using GitLab-managed or vendored models. Administrators must select the same model separately for every sub-feature in a feature group. Add **Apply to all** to instance-level selection for GitLab-managed and vendored models, so that the bulk configuration experience is consistent with the existing experience for self-hosted models. ## Problem to solve On the administrator model selection page for GitLab Self-Managed: - A feature group typically contains multiple sub-features. For example, GitLab Duo Chat includes General Chat, Code Explanation, Test Generation, Refactor Code, and Fix Code. - **Apply to all** is already available for self-hosted models. - **Apply to all** is currently not rendered for GitLab-managed or vendored models. - Administrators must select models one at a time. This is time-consuming, easy to overlook, and can leave sub-features in the same group configured inconsistently. This issue applies to the **instance-level** model configuration page for GitLab Self-Managed. It does not cover top-level group model selection. The corresponding group-level work is tracked in [gitlab-cn/gitlab#5154](https://jihulab.com/gitlab-cn/gitlab/-/work_items/5154). ## Current behavior - Observed in GitLab 19.2.0-jh. - Configuration page: Admin Area > GitLab Duo > Model selection. - When a feature uses a GitLab-managed or vendored model, **Apply to all** is not displayed. - When a feature uses an existing self-hosted model and that model is compatible with every sub-feature in the group, bulk configuration is available. ## Proposal On the instance-level model selection page for GitLab Self-Managed, provide GitLab-managed and vendored models with the same **Apply to all** capability that already exists for self-hosted models: 1. After an administrator selects a model for any sub-feature in a group, they can select **Apply to all**. 2. Enable the bulk action only when the selected model is compatible with every sub-feature in that group. 3. If any sub-feature is incompatible, disable the bulk action and clearly explain why. 4. Reuse the permissions, scope, persistence behavior, and page feedback of the existing instance-level model configuration. 5. Preserve the ability to select a model for each sub-feature individually. ## Acceptance criteria - [ ] On the instance-level model selection page for GitLab Self-Managed, administrators with permission to configure models can use **Apply to all** with a GitLab-managed or vendored model. - [ ] When a group contains multiple sub-features and the selected model is compatible with all of them, **Apply to all** is displayed and enabled. - [ ] Selecting **Apply to all** applies the selected model to every sub-feature in the current group. - [ ] If the selected model is incompatible with any sub-feature, the bulk action is unavailable and a clear explanation is displayed. - [ ] The page clearly reports both successful and failed bulk updates. - [ ] After the page is refreshed, each sub-feature displays the model stored in the saved configuration. - [ ] Existing bulk configuration and individual selection behavior for self-hosted models remain unaffected. - [ ] Permissions and configuration scope remain consistent with the existing instance-level model selection feature. - [ ] Automated tests cover successful bulk updates for vendored models, incompatibility, request failure, permissions, and existing self-hosted model behavior. - [ ] Documentation explains which model sources support instance-level **Apply to all** and any compatibility constraints. ## Out of scope - Top-level group model selection for GitLab Self-Managed, which continues to be tracked in [gitlab-cn/gitlab#5154](https://jihulab.com/gitlab-cn/gitlab/-/work_items/5154). - Skipping incompatible sub-features and performing a partial update. This issue follows the existing behavior: bulk application is available only when the selected model is compatible with every sub-feature in the group. ## Intended users - Sidney (Systems Administrator) - Priyanka (Platform Engineer) - Administrators of GitLab Self-Managed instances ## Feature usage metrics Consider tracking: - How often **Apply to all** is displayed, selected, succeeds, and fails. - The number of sub-features updated by each bulk operation. - How often the bulk action is disabled because of model incompatibility. ## Does this feature require an audit event? Reuse the existing audit mechanism for instance-level model configuration changes. If individual changes generate audit events, a bulk operation should record the user, target model, and affected sub-features. ## Source Translated from [gitlab-cn/gitlab#5248](https://jihulab.com/gitlab-cn/gitlab/-/work_items/5248).