2021-01-25 - Triage report for "group::release"
Hi, @ogolowinski @nicolewilliams @icamacho
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.
Unscheduled ~feature (non-customer)
-
gitlab-org/gitlab#299407 (closed) API support for Change Failure Rate Category:Continuous Delivery, Category:Release Orchestration, GitLab Ultimate, api, auto updated, ~"devops::release", direction, ~"feature", ~"group::release", sectionops -
gitlab-org/gitlab#299353 (closed) Add helper text to deployment frequency metrics Category:Continuous Delivery, UX, candidate13.10, ~"devops::release", ~"feature", frontend, ~"group::release", sectionops -
gitlab-org/gitlab#299293 (moved) Update a Release through Release-CLI Category:Release Orchestration, GitLab Core, GitLab Release CLI, auto updated, ~"devops::release", direction, ~"feature", ~"group::release", sectionops -
gitlab-org/gitlab#299292 Feature Flags: Contextual code references Empty state Category:Feature Flags, GitLab Premium, ~"devops::release", ~"feature", ~"group::release", sectionops -
gitlab-org/gitlab#299285 Display warning when creating namespaces with . (dots) for GitLab Pages Category:Pages, UX, ~"devops::release", ~"feature", ~"group::release", needs team input, sectionops -
gitlab-org/gitlab#299096 (closed) API support for Time to restore service Category:Continuous Delivery, Category:Release Orchestration, GitLab Ultimate, api, ~"devops::release", direction, ~"feature", ~"group::release", sectionops -
gitlab-org/gitlab#299074 Create a release with custom source archives automation:ml, ~"devops::release", ~"feature", ~"group::release", sectionops -
gitlab-org/gitlab#299060 (closed) Get a Release by a tag name through Release-CLI Category:Release Orchestration, GitLab Core, GitLab Release CLI, auto updated, ~"devops::release", direction, ~"feature", ~"group::release", sectionops -
gitlab-org/gitlab#298922 (closed) Switch to the canary environment with a keyboard shortcut GitLab.com Feature Request, automation:ml, ~"devops::release", ~"feature", featureaddition, frontend, ~"group::release", sectionops, shortcuts -
gitlab-org/gitlab#298740 (closed) Expose deployment frequency data through GraphQL endpoint Category:Continuous Delivery, api, automation:ml, ~"devops::release", ~"feature", ~"group::release", sectionops
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.
- Engineering Managers: Please add a severity label for those issues without one
- Product Designers: Please add a severity label to UX ~bug issues without one
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.
| severity1 | severity2 | severity3 | severity4 | No severity | |
|---|---|---|---|---|---|
| priority1 | 0 | 0 | 0 | 0 | 0 |
| priority2 | 0 | 16 | 1 | 0 | 0 |
| priority3 | 0 | 1 | 69 | 2 | 0 |
| priority4 | 0 | 0 | 10 | 49 | 0 |
| No priority | 0 | 0 | 10 | 10 | 13 |
Unscheduled frontend ~bug (non-customer)
-
gitlab-org/gitlab#299066 (closed) Review app button open all modal on branch deploys Category:Review Apps, automation:ml, automation:ml wrong, ~"bug", ~"devops::release", frontend, ~"group::release", sectionops, severity3
Unscheduled ~bug with customer
-
gitlab-org/gitlab#299276 (closed) Pages 502 err Category:Pages, ~"bug", customer, ~"devops::release", ~"group::release", sectionops -
gitlab-org/gitlab#299033 (closed) http Pages not working with domain source config set to gitlab Category:Pages, ~"bug", customer, ~"devops::release", ~"group::release", priority2, sectionops, severity2 -
gitlab-org/gitlab#297496 (closed) database deadlocks updating ci_builds and deployments tables ~"Accepting merge requests", Category:Continuous Delivery, Category:Database, ~"bug", customer, database, ~"devops::release", ~"group::release", sectionops, ~" 🍎 " -
gitlab-org/gitlab#287795 (closed) Reporter MR approval not working Category:Compliance Management, Category:Release Orchestration, ~"bug", customer, ~"devops::release", ~"group::release", sectionops
Unscheduled ~bug (non-customer)
-
gitlab-org/gitlab#297654 (closed) Wiki links to images in Pages site don't load Category:Pages, Category:Wiki, automation:ml, backend, ~"bug", ~"devops::release", ~"group::release", sectionops, severity4
Heatmap for ~missed-SLO bugs
| severity1 | severity2 | severity3 | severity4 | No severity | |
|---|---|---|---|---|---|
| priority1 | 0 | 0 | 0 | 0 | 0 |
| priority2 | 0 | 12 | 0 | 0 | 0 |
| priority3 | 0 | 1 | 0 | 0 | 0 |
| priority4 | 0 | 0 | 0 | 1 | 0 |
| No priority | 0 | 0 | 0 | 0 | 0 |
Heatmap for vintage bugs
| severity1 | severity2 | severity3 | severity4 | No severity | |
|---|---|---|---|---|---|
| priority1 | 0 | 0 | 0 | 0 | 0 |
| priority2 | 0 | 0 | 0 | 0 | 0 |
| priority3 | 0 | 1 | 6 | 0 | 0 |
| priority4 | 0 | 0 | 1 | 3 | 0 |
| No priority | 0 | 0 | 0 | 0 | 1 |
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.yml.
Edited by Itzik Gan Baruch