2019-11-25 - Triage report for "group::portfolio management"
Hi, @kokeefe @donaldcook @johnhope
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)
-
#36767 (closed) Follow-up from "Add relationship and link to new epic to promoted issues" ~"Category:Epics", Enterprise Edition, UX, devopsplan, feature, ~"group::portfolio management"
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 | 2 | 1 | 0 | 0 |
| ~P3 | 0 | 0 | 12 | 3 | 0 |
| ~P4 | 0 | 0 | 1 | 12 | 0 |
| ~"No priority" | 0 | 0 | 0 | 0 | 7 |
Unscheduled frontend ~bug (non-customer)
-
#37091 (closed) "Create New Epic" option fails on Epics at the Sub-Group level ~"Category:Epics", ~"bug", devopsplan, frontend, ~"group::portfolio management", regression, regression:12.5, ~"workflow::In review" -
#37065 (closed) Removing epic / issue from epic does not show error ~"Category:Epics", ~"bug", devopsplan, frontend, ~"group::portfolio management" -
#37064 (closed) Remove buttons in epic tree have weird focus state ~"Category:Epics", UI polish, ~"bug", devopsplan, frontend, ~"group::portfolio management", reproduced on GitLab.com -
#37028 (closed) 'Add epic' placeholder text uses '#' issue notation instead of '&' epic notation ~"Category:Epics", ~"P4", ~"S4", ~"bug", devopsplan, frontend, ~"group::portfolio management" -
#36745 (closed) Tooltip on epic tree is broken ~"Category:Epics", ~"bug", devopsplan, frontend, ~"group::portfolio management", reproduced on GitLab.com -
#36716 (closed) Issue reference changes when adding to epic ~"Category:Epics", ~"bug", devopsplan, frontend, ~"group::portfolio management", reproduced on GitLab.com
Unscheduled ~bug (non-customer)
-
#37062 (closed) Can't add child epic in subgroup ~"Category:Epics", backend, ~"bug", ~"group::portfolio management", reproduced on GitLab.com -
#36924 (closed) Subepic cannot be removed from epic ~"Category:Epics", ~"P3", ~"S3", ~"bug", devopsplan, ~"group::portfolio management"
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: