Issues to apply severity and priority for Frontend

Hi @timzallmann,

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

We would like to ask you to:

  1. 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
  2. Ensure that feature relevant feature labels are added for each bug. This will allow the appropriate team label to be inferred where possible

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.

  • Child epics should use epics icon ~"Accepting merge requests", ~"Plan", ~"bug", epics, frontend, ~"portfolio management", regression, regression:11.7
  • Child epics placeholder should say Paste epic link not Paste issue link ~"Plan", ~"bug", epics, frontend, ~"portfolio management", regression, regression:11.7
  • Account expiration date/time discrepancy ~"Accepting merge requests", ~"Manage", ~"P3", backend, ~"bug", ~"devops:manage", frontend, subscriptions
  • Epic label text color is not consistent with issue label text color ~"Plan", ~"bug", epics, frontend, labels
  • "Don't show me this again" button broken (Epic) ~"Plan", ~"bug", ~"devops:plan", epics, frontend
  • Issue board switcher has blue border on focus ~"Plan", UI polish, boards, ~"bug", ~"devops:plan", frontend
  • Broken empty state image on issue analytics page ~"Accepting merge requests", ~"Plan", ~"bug", frontend, issues, regression, regression:11.5
  • Alert widgets shown for non-licensed instance ~"Monitoring", ~"bug", ~"devops:monitor", frontend, regression, regression:11.5
  • pdf.js bundled GitLab cannot render CJK characters ~"bug", frontend, rich blob viewer
Edited Jan 15, 2019 by André Luís
Assignee Loading
Time tracking Loading