Update decision-making DRIs for severity (!17175) · Merge requests · GitLab.com / Content Sites / handbook

Why is this change being made?

This MR contains some changes I'm proposing as part of the feedback request in gitlab-org/create-stage#13291.

typefeature and typemaintenance issues do not have severities, so we shouldn't list a DRI for severity. This is a minor correction, but it threw me off when reading the table.
bugavailability had no DRI listed for severity, so I'm suggesting to list the EM.

Please verify the check list and ensure to tick them off before the MR is merged.

Provided a concise title for this Merge Request (MR)
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
- Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
Assign reviewers for this MR to the correct
- The when to get approval handbook section explains when DRI approval is required
- The who can approve handbook section explains how to identify the DRI
- If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
- The approver may merge the MR. If they approve but don't merge, you can merge.
For transparency, share this MR with the audience that will be impacted.
- Team: For changes that affect your direct team, share in your group Slack channel
- Department: If the update affects your department, share the MR in your department Slack channel
- Division: If the update affects your division, share the MR in your division Slack channel
- Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
  - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Edited Nov 25, 2025 by François Rosé