Issues to apply severity and priority for Create
Hi @nick.thomas,
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.
-
Adding 52 comments in a batch review breaks the browser ~"Create", ~"bug", regression, regression:11.4 -
Inconsistency in fonts used for branch name and create from fields when creating new branch from UI ~"Create", UI polish, UX, ~"bug" -
Obtain merge commit via API for fast-forward plus squash merge ~"Create", ~"bug", customer, merge requests -
Difference not recognized correctly when resolving merge conflicts ~"Create", ~"bug", ~"code review", ~"devops:create", merge requests, needs investigation -
Gibberish error when making an invalid deploy key ~"Create", UX, ~"bug", ~"devops:create", reproduced on GitLab.com, settings -
Projects::Settings::RepositoryController#show – ActionView::Template::Error: undefined method `access_level' for nil:NilClass ~"Create", auto updated, ~"bug", ~"devops:create" -
URL of commit link is different in preview and published post ~"Create", auto updated, awaiting feedback, ~"bug", merge requests -
Can't view MR diffs beyond 100 files ~"Create", ~"bug", diff, merge requests -
When creating an MR, information is lost after changing branches ~"Create", ~"bug", merge requests, ~"no-priority", ~"no-severity" -
Manual merge request clone commands no longer work ~"Create", ~"bug", ~"no-priority", ~"no-severity"
Edited by Nick Thomas