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:

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.

  • Group settings save button doesn't activate if repository size limit is changed ~"Create", ~"bug", frontend
  • 'you can approve additionally' text still appears after an MR has been merged ~"bug", frontend
  • Batch comments (Review feature) is not respecting code highlighting background from dark themes ~"bug", frontend
  • Improve Related Issues error message when you don't have write permissions ~"Plan", ~"bug", ~"devops:plan", frontend, issues
Assignee Loading
Time tracking Loading