Skip to content

Add information about verification steps to Govern planning

Why is this change being made?

In groupsecurity policies we have been discussing about changes we can do to better verify issues assigned to us. During verification phase we were not properly verifying important scenarios that led to new issues discovered internally or by customers. To mitigate that we would like to add additional step (that is already a part of the Issue Template) to fill the Verification Steps section of the issue with information about possible test cases.

Author Checklist

  • 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.
  • 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
  • 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 Alan (Maciej) Paruszewski

Merge request reports

Loading