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.

  • Merge button disabled after approved ~"Create", approvals, ~"bug", frontend, merge requests
  • When you reorder issues & epics in an epic, the outer box jumps in size a bit ~"Plan", ~"bug", epics, frontend
  • Same note visible twice ~"Create", ~"bug", frontend
  • Changing weight of newly created issue fails on issue board sidebar ~"Issue Boards", ~"Plan", ~"bug", ~"devops:plan", frontend, issue weight, reproduced on GitLab.com
  • Can't reopen merged Merge Request: cannot transition via "reopen" ~"Create", ~"S2", ~"bug", frontend
  • Broken empty state image on issue analytics page ~"Accepting merge requests", ~"Plan", ~"bug", frontend, issues, regression, regression:11.5
  • pdf.js bundled GitLab cannot render CJK characters ~"bug", frontend, rich blob viewer
  • Adding related issue does not complete todo ~"Plan", auto updated, awaiting feedback, ~"bug", ~"devops:plan", frontend
Assignee Loading
Time tracking Loading