Skip to content

Pipeline Security: Removing stack-ranked issue system

Scott Hampton requested to merge shampton-pipeline-security-remove-stack-ranking into main

Why is this change being made?

Currently we have a "stack-ranked" issue system where team members can take the next top-ranked issue in our workflow board. The purpose behind this was to make it easy for developers to see what the next priority is when taking on new work.

However, keeping the columns up to date on stack ranking requires a lot of dedication and time. As a result, these columns were often out of date which caused confusion among engineers on which issues were actually the next priority.

This merge request removes that system, and reverts back to our old system of working directly from the milestone tracking board. If there are no issues to take on in the milestone board, engineers should look to the issues that are planned for the upcoming milestone.

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
  • 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
Edited by Scott Hampton

Merge request reports