2020-11-02 - Triage report for "group::product planning"
Hi, @mjwood @johnhope @donaldcook @uhlexsis @mikelong
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.
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
-
gitlab-org/gitlab#273724 (closed) Add include_descendantsparameter to Group Milestones API customer, devopsplan, ~"feature", groupproduct planning
Unscheduled ~feature (non-customer)
-
gitlab-org/gitlab#273786 Enable users to understand epic | sub-epic hierarchy from board with epic swimlanes applied ~"Actionable Insight", ~"Category:Epics", UX, backend, devopsplan, ~"feature", frontend, groupproduct planning -
gitlab-org/gitlab#273779 (closed) Better visual grouping of swimlane rows to indicate they are related ~"Actionable Insight", UI polish, UX, devopsplan, ~"feature", frontend, groupproduct planning -
gitlab-org/gitlab#273459 (closed) Allow NOT filter in Epic Roadmap view ~"Category:Epics", devopsplan, ~"feature", groupproduct planning, sectiondev -
gitlab-org/gitlab#273165 Allow Service Desk only projects (no repository, etc.) Category:Service Desk, devopsplan, ~"feature", featureaddition, groupproduct planning, sectiondev -
gitlab-org/gitlab#272987 Allow to forward e-mails to service desk and associate them with the original e-mail address Category:Service Desk, devopsplan, ~"feature", groupproduct planning, sectiondev -
gitlab-org/gitlab#272484 (closed) Allow Service Desk to create Incidents Category:Service Desk, devopsplan, ~"feature", groupproduct planning, sectiondev
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 | 2 | 1 | 0 | 0 |
| priority3 | 0 | 1 | 36 | 2 | 0 |
| priority4 | 0 | 0 | 0 | 16 | 0 |
| No priority | 0 | 0 | 4 | 2 | 7 |
Unscheduled frontend ~bug (non-customer)
-
gitlab-org/gitlab#273817 (closed) Roadmaps: Epics disappear after scrolling ~"bug", devopsplan, frontend, groupproduct planning
Unscheduled ~bug with customer
-
gitlab-org/gitlab#230736 (closed) Bulk label editing appends descriptions to epics ~"Category:Epics", ~"bug", customer, devopsplan, groupproduct planning
Unscheduled ~bug (non-customer)
-
gitlab-org/gitlab#270887 (closed) Cannot promote an issue to an epic using /promote quick action ~"Category:Epics", ~"bug", devopsplan, groupproduct planning, sectiondev, severity3
Heatmap for ~missed-SLO bugs
| severity1 | severity2 | severity3 | severity4 | No severity | |
|---|---|---|---|---|---|
| priority1 | 0 | 0 | 0 | 0 | 0 |
| priority2 | 0 | 1 | 0 | 0 | 0 |
| priority3 | 0 | 1 | 0 | 0 | 0 |
| priority4 | 0 | 0 | 0 | 0 | 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 | 0 | 5 | 0 | 0 |
| priority4 | 0 | 0 | 0 | 3 | 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.yml.