Update CMOC Stakeholder Notification process
Why is this change being made?
Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.
Currently we use Incident Notifier to notify stake holders in 2 slack channels. The field names are open to interpretation resulting in some inconsistency with the process.
This will define what is expected in each field and what can be expected when submitting a notification using the tool.
Author and Reviewer Checklist
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 Directly Responsible Individual/s (DRI) - 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 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
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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 -
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
-
Merge request reports
Activity
assigned to @cmarais
requested review from @erikamiklos
️ Pipeline Failure - Markdown Lint ErrorsMarkdown Lint has reported errors and as a result the pipeline has failed. Once the pipeline completes you'll find the code quality report above which can link you to where the error is in your code. Additionally below you'll find a table of the errors. The table has links to the markdown lint rules so you can find more information on how to fix the issue(s).
Rule File Line Error Help MD004 content/handbook/support/workflows/cmoc_workflows.md 228 Unordered list style [Expected: dash; Actual: asterisk] ️MD004 content/handbook/support/workflows/cmoc_workflows.md 229 Unordered list style [Expected: dash; Actual: asterisk] ️MD004 content/handbook/support/workflows/cmoc_workflows.md 230 Unordered list style [Expected: dash; Actual: asterisk] ️MD004 content/handbook/support/workflows/cmoc_workflows.md 231 Unordered list style [Expected: dash; Actual: asterisk] ️MD004 content/handbook/support/workflows/cmoc_workflows.md 232 Unordered list style [Expected: dash; Actual: asterisk] ️If you need more help please reach out on Slack in #mr-buddies or #handbook.
- Resolved by Erika Miklos
@cmarais The only comment from my side is that in your list the "severity" line is missing a dot at the end of the sentence and I'd add the e.g parts in a ( ) . Example
-
**Incident Slack Channel**: Link to the incident slack channel. (eg: `#incident-12345`)
-
**Summary**: Brief summary, you can make it the same as the CMOC notice.
-
**Severity**: Select the same severity as the Incident
-
**Production issue**: Link to the incident issue. eg: `https://gitlab.com/gitlab-com/gl-infra/production/-/issues/12345\`
-
**Incident Slack Channel**: Link to the incident slack channel. eg: `#incident-12345`
-
**Status Page**: Click on the incident to expland the full status page url. eg: `https://status.gitlab.com/pages/incident/xxxxxxxx/xxxxxxxx\`
-
mentioned in commit 043e6933