Update Compliance deliverable process
What does this MR do and why?
In Remove Compliance group from missed resource flow (!2529 - merged) we introduced a process to skip adding ~missed:X.Y labels to issues that were not ~goal::complete.
This MR updates this to use the Deliverable label instead of ~goal::complete, as Deliverable label is more widely used. This will make it easier for a wider discussion about making this standard for all groups.
This all updates the remove labels process to remove Deliverable and ~goal::XX labels at the end of a milestone. Resetting expectations for next milestone
Update 3 files
- /policies/stages/hygiene/missed-resources.yml
- /lib/missed_resource_helper.rb
- /spec/lib/missed_resource_helper_spec.rb
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-policies-with-a-dry-run on how to perform dry-runs for new policies.
See https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/reactive/best_practices.md#use-the-sandbox-to-test-new-processors on how to make sure a new processor can be tested.
Action items
-
If adding environment variables for reactive processors, update config/triage-web.yaml
and.gitlab/ci/triage-web.yml
-
(If applicable) Add documentation to the handbook pages for Triage Operations => - (If applicable) Identify the affected groups and how to communicate to them:
-
/cc @ person_or_group
=> -
Relevant Slack channels => -
Engineering week-in-review
-