2019-11-18 - Triage report for "group::package"
This is a group or stage level triage package that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:
Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:
- Determine if the issue should be closed if it is no longer relevant or a duplicate.
- If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
- Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
- Once a milestone has been assigned please check off the box for that issue.
- Please work with your team to complete the list by the due date set.
Unscheduled feature (non-customer)
-
#35922 (closed) Package: Display Approved or Verified UI element to individual packages Category:Container Registry, Category:Package Registry, Package Repositories, devopspackage, feature, ~"group::package" -
#35633 (closed) Make it easier to publish and use NPM packages from GitLab's NPM registry devopspackage, feature, ~"group::package" -
#35527 (closed) Improve group and project level package api Category:Package Registry, backend, devopspackage, feature, ~"group::package", workflowscheduling
Bug Section
For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.
Heatmap for all bugs
Bugs for their priority and severity label are counted here. Every bug should have severity and priority labels applied. Please take a look at the bugs which fall into the columns indicating that the priority or severity labels are currently missing.
| ~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
|---|---|---|---|---|---|
| ~P1 | 1 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 3 | 0 | 0 | 0 |
| ~P3 | 0 | 1 | 27 | 0 | 0 |
| ~P4 | 0 | 0 | 3 | 10 | 0 |
| ~"No priority" | 0 | 0 | 0 | 1 | 2 |
Unscheduled ~bug with customer
-
#36076 (closed) Maven Repo: Could not resolve dependencies - Could not find artifact Category:Package Registry, ~"bug", customer, devopspackage, ~"group::package" -
#36026 (closed) GitLab incorrectly deletes tags when external registry storage deletion is disabled Category:Container Registry, ~"P2", ~"S2", ~"bug", customer, devopspackage, ~"group::package", workflowscheduling
Unscheduled ~bug (non-customer)
-
#36183 (closed) Possible rails validation problem with updating groups Category:Package Registry, ~"bug", devopspackage, ~"group::package", regression, regression:12.5, workflowverification -
#36029 (closed) (confidential) ~"(confidential)" -
#34847 (closed) Docs feedback: Redirects after transfer do not mention container registry ~"P4", ~"S3", ~"bug", devopspackage, docsimprovement, ~"group::package" -
#33409 (closed) Docs feedback: NPM registry documentation is not clear / wrong Category:Package Registry, ~"P3", ~"S3", ~"bug", devopspackage, ~"docs:fix", ~"group::package"
Heatmap for ~missed-SLO bugs
| ~S1 | ~S2 | ~S3 | ~S4 | |
|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 2 | 0 | 0 |
| ~P3 | 0 | 0 | 0 | 0 |
| ~P4 | 0 | 0 | 0 | 0 |
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: