2019-09-02 - Triage report for "group::knowledge"
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.
Unscheduled feature (non-customer)
-
#13490 (closed) Design view needs more context Create [DEPRECATED], UX, ~"design management", devopscreate, feature, groupknowledge -
#13371 (closed) Should we return the new version from the design upload service? ~"GitLab Enterprise Edition", backend, ~"design management", devopscreate, feature, groupknowledge -
#14368 (closed) WYSIWYG editor for wikis Create [DEPRECATED], UX, auto updated, devopscreate, feature, frontend, groupknowledge, markdown, potential proposal, ~"wiki" -
#14211 (closed) Allow title case in Wiki page title Create [DEPRECATED], auto updated, devopscreate, feature, groupknowledge, potential proposal, ~"wiki"
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 | 1 | 0 | 0 | 0 | 0 |
| ~P2 | 2 | 1 | 0 | 0 | 0 |
| ~P3 | 0 | 0 | 2 | 0 | 0 |
| ~P4 | 0 | 0 | 3 | 0 | 0 |
| ~"No priority" | 0 | 0 | 0 | 0 | 1 |
Unscheduled ~bug (non-customer)
-
#13495 (closed) Design versions should not have duplicate ids and have version included in id Create [DEPRECATED], backend, ~"bug", ~"design management", devopscreate, groupknowledge -
#13867 (closed) Wiki pagetitle with hyphenated words Create [DEPRECATED], ~"P4", ~"S3", backend, ~"bug", default-priority, default-severity, devopscreate, groupknowledge, ~"wiki"
Heatmap for ~missed-SLO bugs
| ~S1 | ~S2 | ~S3 | ~S4 | |
|---|---|---|---|---|
| ~P1 | 1 | 0 | 0 | 0 |
| ~P2 | 0 | 0 | 0 | 0 |
| ~P3 | 0 | 0 | 0 | 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: