Issues to apply severity and priority for Quality

Hi @meks,

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.

  • Test plan for deprecating TLS 1.0 and moving to TLS 1.1 in GitLab.com Quality, security
  • Test run object (or issue verification object generally) GitLab Ultimate, ~"Plan", Quality, ~"devops:plan", direction
  • [Rails5] Couldn't find User with 'id'=1289 Quality, backend, ~"dependency update", rails5, test
  • EE test jobs time out Quality, ~"broken master", ci-build, test
  • Extract EE specific files/lines for YAML files Quality
  • Configure Gitlab QA for review apps QA, Quality, ~"review apps"
  • Transient order-dependent failure in spec/features/merge_request/user_merges_when_pipeline_succeeds_spec.rb Quality, ~"broken master"
  • Extract EE specific files/lines for . Quality, ~"backstage"
  • Extract EE specific files/lines for Discussion app/models ~"Plan", Quality, backend, ~"backstage"
  • Extract EE specific files/lines for Platform app/models ~"Platform", Quality, backend, ~"backstage"
Edited Oct 01, 2018 by Rémy Coutable
Assignee Loading
Time tracking Loading