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.
-
Fullscreen layout on Issue Boards has scrollbar on html element ~"bug", frontend -
Double timeline entry and missing reply holder when you start a discussion on dashboard snippets ~"bug", frontend -
Double timeline entry when you start a discussion on commits ~"bug", frontend -
Inconsistent rebase status in merge request ~"Create", ~"bug", customer, ~"devops:create", frontend, merge requests, needs investigation -
wiki: no visual differentiation between active page and directories ~"Create", UX, ~"bug", ~"devops:create", frontend, reproduced on GitLab.com, ~"wiki" -
Read more link in mobile view of project overview is always visible ~"Manage", ~"bug", ~"devops:manage", frontend, project -
Diffs file tree browser: cannot quick-switch back to previously selected file when scrolling away ~"Create", ~"bug", ~"devops:create", diff, frontend, merge requests -
Can't reply to a resolved single-comment discussion in a merge request without unresolving it first ~"Accepting merge requests", ~"Create", UX, ~"bug", frontend, merge requests, regression, regression:11.5 -
Line numbers are misaligned in file blame view ~"Create", ~"bug", ~"devops:create", frontend -
Filter out "Refused to send beacon to 'http://gj.track.uc.cn/" errors in Sentry Quality, ~"bug", frontend