2019-10-21 - Triage report for "group::health"
Hi, @sarahwaldner @sengelhard @ClemMakesApps
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
-
#27581 (closed) Allow for non-admin users to access broadcast messages via the API api, backend, customer, devopsmonitor, feature, ~"group::health"
Unscheduled feature (non-customer)
-
#34113 (closed) Add correlation ID to 500 page response devopsmonitor, ~"error tracking", feature, gitlab.com, ~"group::health", internal customer -
#34037 (closed) Link to relevant GitLab issue from GitLab.com 500 page devopsmonitor, ~"error tracking", feature, gitlab.com, ~"group::health" -
#32067 (closed) Allow users to set Ops Dashboard as default home page backend, devopsmonitor, feature, frontend, ~"group::health", operations dashboard -
#32037 (closed) Provide an API to customize repository Operations integration Category:Error Tracking, devopsmonitor, feature, ~"group::health" -
#31284 (closed) Provide a consolidated timeline view in Incident after action devopsmonitor, direction, feature, ~"group::health", ~"incident management" -
#31283 (closed) Suggest Alert and Runbook changes during Incident after action devopsmonitor, direction, feature, ~"group::health", ~"incident management" -
#31282 (closed) Display last deployed commit info in incident templates devopsmonitor, direction, feature, ~"group::health", ~"incident management" -
#30712 (closed) Dogfood: Security Pager Dogfooding, DogfoodingRebuild in GitLab, devopsmonitor, feature, ~"group::health", internal customer -
#24981 (closed) 500 Error pages should show GitLab status Category:Error Tracking, UX, devopsmonitor, feature, frontend, gitlab.com, ~"group::health", infrastructure, ~"search"
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 | 0 | 0 | 0 | 0 |
| ~P3 | 0 | 0 | 2 | 0 | 0 |
| ~P4 | 0 | 0 | 0 | 2 | 0 |
| ~"No priority" | 0 | 0 | 0 | 0 | 2 |
Unscheduled ~bug with customer
-
#34002 (closed) Custom metric in the wrong graph. Charts, ~"bug", customer, devopsmonitor, ~"group::health"
Unscheduled ~bug (non-customer)
-
#34059 (closed) Improve process documentation for adding Sentry integration by recommending creating a new project Category:Error Tracking, ~"bug", devopsmonitor, ~"docs-update", documentation, ~"group::health"
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: