Create group issues requiring attention
Hi @jramsay,
Here is a list of feature proposals without a milestone.
We would like to ask you to determine whether this issue should be scheduled or closed. For each issue please:
- Close the issue out if it is no longer relevant or a duplicate.
- Assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.
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.
-
#12010 (closed) Finish review and reassign ~"Create", devopscreate, feature -
#11983 (closed) Line-by-Line code coverage results displayed in a Merge Request's changes tab. ~"Create", ~"code review", devopscreate, feature, groupsource code, merge requests -
#11862 (moved) Files in the file browser on merge requests are buttons which makes it hard to open them in a new tab ~"Create", awaiting feedback, devopscreate, feature, merge requests -
#11861 Merge requests should record and display read / unread status for all files ~"Create", awaiting feedback, devopscreate, feature, merge requests -
#11860 (moved) IntelliJ integration for GitLab merge requests ~"Create", devopscreate, feature, merge requests -
#11859 (closed) Formal merge request disapproval ~"Create", devopscreate, feature, merge requests -
#11858 (closed) Ability to create groups of users that can be added to a merge request ~"Create", devopscreate, feature -
#11857 (closed) Categories for merge request comments ~"Create", devopscreate, feature -
#11712 (closed) Allow multiple code owners rules to match a file ~"Create", devopscreate, feature, groupsource code, merge requests -
#11557 Groups inheritance for approvals ~"Create", approvals, devopscreate, feature, groupsource code, merge requests -
#11550 (closed) When mirroring repo don't use name of user configuring the mirror for activity ~"Create", customer, devopscreate, feature, ~"mirror" -
#11530 Modify "merge_status" or add additional attribute in Merge Request API to include approvers and jobs status ~"Create", approvals, feature, merge requests -
#11462 (closed) Ability in GitLab API to control "Enable self approval of merge requests" ~"Create", api, approvals, feature, merge requests -
#11393 (closed) Complex merge order dependencies ~"Create", devopscreate, feature, merge requests -
#11277 Link reviews to a set of commits, instead of to a merge request ~"Create", GitLab Premium, ~"code review", devopscreate, feature, merge requests
Hi @andr3,
Here is a list of frontend bugs without severity and priority for the team.
We would like to ask you to work with your team to triage the issues in this list. For each issue please:
- Close the issue if it is no longer relevant or a duplicate.
- Assign a Priority and a Severity Label.
- Assign either a versioned milestone or to the %Backlog milestone.
The definition of these labels are defined at:
- Priority Labels (~P1 / ~P2 / ~P3 / ~P4)
- Severity Labels (~S1 / ~S2 / ~S3 / ~S4)
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.
-
#11730 (closed) Multiple assignees merge request system notes bug ~"Create", ~"bug", devopscreate, frontend, merge requests -
#9650 (closed) Same note visible twice ~"Create", ~"bug", frontend -
#6619 (closed) Cannot display approve merge requests in IE11 ~"Create", approvals, awaiting feedback, browser:ie11, ~"bug", frontend, merge requests -
#5497 (closed) Improve role/user/group selection for protected branches/tags ~"Accepting merge requests", ~"Create", ~"Platform [DEPRECATED]", UX, ~"bug", customer, frontend, repository, settings
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 the issues in this list. For each issue please:
- Close the issue if it is no longer relevant or a duplicate.
- Assign a Priority and a Severity Label.
- Assign either a versioned milestone or to the %Backlog milestone.
The definition of these labels are defined at:
- Priority Labels (~P1 / ~P2 / ~P3 / ~P4)
- Severity Labels (~S1 / ~S2 / ~S3 / ~S4)
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.
-
#11997 (closed) Error copying LFS objects on pull mirroring ~"Create", ~"bug", customer, devopscreate, groupsource code, ~"import", ~"lfs", ~"mirror" -
#11887 (closed) "Change approval configuration" API not allowing to change "approvals_required". ~"Create", ~"S2", approvals, ~"bug", customer, devopscreate -
#11874 (closed) Lower UpdateAllMirrorsWorker
rescheduling threshold to ensure queue is always as full as can be ~"Create", backend, ~"bug", devopscreate, groupsource code, ~"mirror" -
#11808 Required CODEOWNERS approvers not updated when CODEOWNERS changes ~"Create", approvals, ~"bug", devopscreate, merge requests -
#11792 Repository size check will be inaccurate when using Git Object Pools ~"Create", ~"bug", devopscreate -
#6776 (closed) "should_remove_source_branch" is being ignored when accepting MR from API. ~"Create", api, ~"bug", customer, devopscreate, groupsource code, merge requests
@DouweM
/ccThis is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook: