Configure group issues requiring attention

Hi @DylanGriffith,

Here is a list of bugs without severity and priority for the team.

We would like to ask you to work with your team to triage the issues in this list. For each issue please:

  • Close the issue if it is no longer relevant or a duplicate.
  • Assign a Priority and a Severity Label.
  • Assign either a versioned milestone or to the %Backlog milestone.

The definition of these labels are defined at:

  • Priority Labels (~P1 / ~P2 / ~P3 / ~P4)
  • Severity Labels (~S1 / ~S2 / ~S3 / ~S4)

For the issues triaged please check off the box in front of the given issue.

Please work with your team to complete the list this week.

  • #11847 (closed) Mattermost notifications for merge request approvals use the wrong text ~"Configure", ~"S4", ~"bug", ~"devops::configure"

We're only listing 15 issues here, and here's the heat map for the full distribution:

~S1 ~S2 ~S3 ~S4
~P1 0 0 0 0
~P2 0 0 0 0
~P3 0 0 0 0
~P4 0 0 0 0
~"No priority" 0 0 0 1


This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:

  • https://about.gitlab.com/handbook/engineering/quality/guidelines/triage-operations/#current-packages
Edited Jun 24, 2019 by Dylan Griffith (ex GitLab)
Assignee Loading
Time tracking Loading