2019-12-02 - Triage report for "group::testing"
Hi, @jheimbuck_gl @erushton @dcipoletti
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.
Feature Proposal Section
For the following feature proposals. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.
Unscheduled feature with customer
-
#9784 (closed) Allow sast and codequality without docker in docker enabled Category:Code Quality, Category:SAST, Enterprise Edition, customer, devopssecure, feature, grouptesting
Unscheduled feature (non-customer)
-
#37326 Show artifacts exposed via exposed_asalso in the pipeline view like J-Unit tests do. ~"artifacts", devopsverify, feature, grouptesting, pipeline
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 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 4 | 0 | 0 | 0 |
| ~P3 | 0 | 0 | 11 | 0 | 0 |
| ~P4 | 0 | 0 | 1 | 6 | 0 |
| ~"No priority" | 0 | 0 | 1 | 0 | 1 |
Unscheduled ~bug with customer
-
#37365 (closed) ActionView::Template::Error: XML parsing failed Category:Continuous Integration, ~"P3", ~"S3", ~"bug", customer, devopsverify, grouptesting
Unscheduled ~bug (non-customer)
-
#37347 (closed) Incorrectly formatted JUnit test results cause the corresponding pipeline page to return a 500 Category:Continuous Integration, ~"Category:Unit Testing", ~"S3", ~"bug", devopsverify, grouptesting -
#37129 (closed) Artifact paths not properly parsed for expose_as Category:Continuous Integration, ~"artifacts", ~"bug", devopsverify, grouptesting
Heatmap for ~missed-SLO bugs
| ~S1 | ~S2 | ~S3 | ~S4 | |
|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 1 | 0 | 0 |
| ~P3 | 0 | 0 | 2 | 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: