Add documentation for blocking labels for incident and change issues
Why is this change being made?
- We are now adding additional logic to ease some of the difficulty when dealing with incidents or change issues that are of high criticality but not be blocking in nature
- Updates our incident pages with details on the auto application of the block labels and when they shall be removed
- Updates the change management page with similar information
Addresses: gitlab-com/gl-infra&736 (closed)
Milestones
-
This is reviewed -
Tooling updates are complete - gitlab-com/gl-infra&736 (closed) -
This is merged -
This is advertised
Author Checklist
-
Provided a concise title for the 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.
-
Assign reviewers for this change to the correct DRI(s) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
- If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR. - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by John Skarbek