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:
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.
-
Rendering issue in Kubernetes -> Applications Settings ~"bug", frontend, regression, regression:11.2 -
Geo: [Admin > Geo Nodes > Projects] Expanding the "More" section in Failed tab isn't working ~"Geo", Geo Administration, ~"bug", frontend, ~"no-priority", ~"no-severity", regression, regression:11.3 -
Logs view scrolls off the top of the page Deliverable, ~"Monitoring", ~"bug", frontend, ~"no-priority", ~"no-severity" -
Adding issues to a list where the board is scoped to Any,None, or0weights returns 422 (Unprocessable Entity) ~"Plan", boards, ~"bug", customer, frontend, issue weight, ~"no-priority", ~"no-severity" -
"Storage config" section makes no sense for primary ~"Geo", ~"Geo Validation/Accuracy", ~"bug", frontend, ~"no-priority", ~"no-severity" -
Clicking "Cancel" on remove-approver prompt doesn't actually cancel ~"Create", awaiting feedback, ~"bug", frontend, merge requests, settings -
Roadmaps page has no scrollbar ~"Plan", awaiting feedback, ~"bug", frontend, roadmaps -
Overview of locked files displays HTML instead of relative time srting ~"Platform", ~"S4", ~"bug", file locking, frontend, reproduced on GitLab.com