Deprecate ability for top level group owners to create custom roles
For guidance on the overall deprecations, removals and breaking changes workflow, please visit Breaking changes, deprecations, and removing features
Deprecation Summary
On self-managed, top-level group owners will no longer be able to create custom roles. This functionality is moving to the instance level, where only admins will be able to create custom roles. Group owners will still be able to assign custom roles at the group level.
Group owners on GitLab.com can continue to manage custom roles and assign at the group level.
Breaking Change
-
Admins can now create custom roles at the instance level, while group owners can assign custom roles at the group level.
-
If using the API to manage custom roles on a self-managed instance, a new instance endpoint has been added and is required to continue API operations.
Before 17.0 After 17.0 - List all member roles on the group -
GET /api/v4/groups/:id/member_roles
- Add a member role to the group -
POST /api/v4/groups/:id/member_roles
- Remove member role of the group -
DELETE /api/v4/groups/:id/member_roles/:member_role_id
- List all member roles on the instance -
GET /api/v4/member_roles
- Add a member role to the instance -
POST /api/v4/member_roles
- Remove member role of the instance -
DELETE /api/v4/member_roles/:id
- List all member roles on the group -
Affected Topology
Self-managed users
Affected Tier
Ultimate
Checklists
Labels
-
This issue is labeled deprecation, and with the relevant ~devops::
,~group::
, and~Category:
labels. -
This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.
Timeline
Please add links to the relevant merge requests.
-
As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0
–14.8
is the third milestone preceding the major release):-
A deprecation announcement entry has been created so the deprecation will appear in release posts and on the general deprecation page. -
Documentation has been updated to mark the feature as deprecated.
-
-
On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post. -
On the major milestone: -
The deprecated item has been removed. -
If the removal of the deprecated item is a breaking change, the merge request is labeled breaking change.
-
Mentions
-
Your stage's stable counterparts have been @mentioned
on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.- To see who the stable counterparts are for a product team visit product categories
- If there is no stable counterpart listed for Sales/CS please mention
@timtams
- If there is no stable counterpart listed for Support please mention
@gitlab-com/support/managers
- If there is no stable counterpart listed for Marketing please mention
@cfoster3
- If there is no stable counterpart listed for Sales/CS please mention
- To see who the stable counterparts are for a product team visit product categories
-
Your GPM has been @mentioned
so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.