Skip to content

Filter by Deliverable Label for Group::Workspace Quad Planning

Valerie Burton requested to merge update-expected-labels-for-group-workspace into master

What does this MR do and why?

This MR updates the quad planning policy for group::workspace to filter by issues that use the Deliverable label rather than workflow::ready for development.

This is because during milestone planning, more issues could be assigned the workflow::ready for development label than will actually be worked on in that milestone due to capacity. The workflow::ready for development label may not always be used either, causing issues to be missed on the Quad Planning report.

By filtering by the Deliverable label instead, this will ensure the SET will review the issues that are committed to be worked on in the current and upcoming milestones.

The quad-planning::ready label can also be used, if needed, for issues that we'd like input from the SET on that may not be assigned the Deliverable label yet.

Expected impact & dry-runs

These are strongly recommended to assist reviewers and reduce the time to merge your change.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-with-a-dry-run on how to perform dry-runs.

Action items

  • (If applicable) Add documentation to the handbook pages for Triage Operations =>
    • Note: If MR is approved and merged, I will create a follow-up MR to update the following docs with a group-specific Quad Planning section
  • (If applicable) Identify the affected groups and how to communicate to them:
    • /cc @person_or_group =>
    • Relevant Slack channels =>
    • Engineering week-in-review
Edited by Valerie Burton

Merge request reports