Skip to content

Draft: Create commerce integrations group in Stages.yml

Why is this change being made?

As part of the ramping up of the Commerce Integrations team we're starting to assign tickets to ~"group::commerce integrations" for planning and organizational purposes. However as was pointed out in https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/5464#note_1106668836 the data changes needed to support triage and other automation does not yet exist. This MR adds the needed group meta information to support existing tooling understanding the new group.

The Triage-Ops companion issue to this can be found at:

gitlab-org/quality/triage-ops#1131 (closed)

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 Isabel Sandin

Merge request reports