Create group issues requiring attention
Heat map for bugs:
| ~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
|---|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 11 | 2 | 0 | 0 |
| ~P3 | 0 | 4 | 64 | 0 | 0 |
| ~P4 | 0 | 0 | 25 | 22 | 0 |
| ~"No priority" | 0 | 0 | 2 | 1 | 7 |
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.
-
#12641 (closed) Creating GitLab index fails on Elasticsearch 7 ~"Create", customer, devopscreate, ~"elasticsearch", feature, ~"group::editor", ~"search" -
#12551 (closed) API support for blocking merge requests ~"Create", api, backend, devopscreate, feature, groupsource code, merge requests -
#12549 (closed) Include blocking merge requests in project import/export ~"Create", backend, devopscreate, feature, groupsource code, merge requests, ~"project export", ~"project import" -
#12333 (closed) elastic: snippet search should fully respect elasticsearch selective search ~"Create", devopscreate, ~"elasticsearch", feature, ~"group::editor" -
#12297 (closed) Get merge request review information through API ~"Create", api, ~"code review", devopscreate, feature, groupsource code, merge requests -
#12147 Add repository code indexing for tags to elasticsearch ~"Create", devopscreate, ~"elasticsearch", feature, ~"group::editor", ~"search" -
#12123 Encrypt username and password when using Elasticsearch integration ~"Create", customer, devopscreate, ~"elasticsearch", feature, ~"group::editor", ~"search" -
#12011 (closed) Promote Source/Target Branch Fields in Merge Request Form ~"Create", devopscreate, feature, groupsource code, merge requests -
#11861 Merge requests should record and display read / unread status for all files ~"Create", awaiting feedback, devopscreate, feature, 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.
-
#12632 (closed) Only allow Starting a new discussion on a line that doesn't yet have a Draft note created on it ~"Accepting merge requests", ~"Create", ~"UX ready", ~"bug", devopscreate, frontend, groupsource code, ~"workflow::In dev" -
#12497 (closed) 'Hide Whitespace Changes' checkbox has no effect, must refresh page to see result ~"Create", ~"bug", ~"code review", devopscreate, diff, frontend, groupsource code, merge requests -
#12302 (closed) In commit detail page, drop down list layout issue. ~"Create", ~"S4", ~"bug", devopscreate, frontend, groupsource code -
#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.
-
#12492 (closed) Merge request push rules error not notified in fast-forward mod ~"Create", ~"S3", ~"bug", devopscreate, groupsource code, merge requests -
#12218 (closed) Approvers show up as "none" even though one is assigned ~"Create", ~"S3", approvals, ~"bug", devopscreate, groupsource code, merge requests -
#5800 (closed) Changing target branch during merge request creation resets previous fields ~"Create", auto updated, awaiting feedback, ~"bug", customer, devopscreate, merge requests
/cc @DouweM
This 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: