Issues to apply severity and priority for Create

Hi @nick.thomas,

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 and add a severity label (~S1 / ~S2 / ~S3 / ~S4) and a priority label (~P1 / ~P2 / ~P3 / ~P4) to the issues in this list.

The definition of these labels are defined at:

  • Priority Labels
  • Severity Labels

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.

  • Suggesting code owners as approvers does not work in Starter ~"Create", GitLab Starter, approvals, backend, ~"bug", customer, ~"devops:create", regression, regression:11.4
  • System footer obscures button in merge request ~"Create", ~"bug", ~"devops:create", merge requests
  • Pull mirroring with SSH authentication may not update every branch ~"Create", ~"bug", ~"devops:create", ~"mirror", needs investigation
  • Batch Comments in MR: Multiple discussions shown on clicking 'submit review' ~"Create", ~"bug", merge requests
  • "Something went wrong during merge pre-receive hook" on merge request due to the "Prevent committing secrets to Git" setting on upstream ~"Create", ~"bug", ~"devops:create", forking, repository
Edited Nov 05, 2018 by Nick Thomas
Assignee Loading
Time tracking Loading