Skip to content

Resolve "Add guidance on creating issue for EA team"

Why is this change being made?

Add guidance on creating issue for EA team.

I've currently been getting pings in Slack for investigative issues and I think it would be best to direct team members to this section https://about.gitlab.com/handbook/engineering/quality/engineering-analytics-team/#how-to-engage-with-us that has guidance on how to open a ticket and which labels to apply.

Author Checklist

  • Provided a concise title for the 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 change to the correct DRI(s)
    • 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 in 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.

Closes #12751 (closed) Closes https://gitlab.com/gitlab-com/engineering-analytics/-/issues/27

Edited by Mek Stittri

Merge request reports

Loading