2020-07-06 - Triage report for "group::fulfillment"
Hi, @amandarueda @jameslopez @chris_baus @jackib @mkarampalas @vincywilson
This is a group or stage level triage report 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.
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 | 0 | 1 | 0 | 0 | 0 |
~P2 | 0 | 1 | 1 | 0 | 0 |
~P3 | 0 | 0 | 5 | 0 | 0 |
~P4 | 0 | 0 | 0 | 0 | 0 |
No priority | 0 | 0 | 2 | 0 | 2 |
Unscheduled ~bug (non-customer)
-
#224145 (confidential) ~"(confidential)" -
#11298 (closed) Flaky spec: "API::Namespaces PUT :id/gitlab_subscription when authenticated as an admin when namespace is not found returns a 404 error" / ee/spec/requests/api/namespaces_spec.rb:272 ~"Category:Billing", Engineering Productivity, Enterprise Edition, ~"P3", Quality, ~"S3", ~"bug", ci-build, devopsgrowth, failureflaky-test, ~"group::fulfillment", ~"quarantined test", test
Heatmap for ~missed-SLO bugs
~S1 | ~S2 | ~S3 | ~S4 | No severity | |
---|---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 | 0 |
~P2 | 0 | 1 | 1 | 0 | 0 |
~P3 | 0 | 0 | 1 | 0 | 0 |
~P4 | 0 | 0 | 0 | 0 | 0 |
No priority | 0 | 0 | 0 | 0 | 0 |
This is a group level triage report that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:
If assignees or people mentioned in this individual triage report need to be amended, please edit group_definition.rb.