2019-08-05 - Triage report for "group::team planning"
Hi, @gweaver @donaldcook @smcgivern
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:
- https://about.gitlab.com/handbook/engineering/quality/guidelines/triage-operations/#current-packages
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
-
#11950 (closed) Allow users to create an issue from within an Epic ~"Plan", customer, devopsplan, feature, ~"group::team planning" -
#11948 (closed) Ability to associate issue with an Epic from the issue ~"Plan", customer, devopsplan, feature, ~"group::team planning" -
#11590 (closed) Support hundredths decimal place in issue weights ~"Plan", backend, customer, devopsplan, feature, frontend, ~"group::team planning", issue weight, issues
Unscheduled feature (non-customer)
-
#13243 (closed) Provide alternative constructs and progress reporting other than milestones for organizing a team's workflow ~"Category::Issue Boards", customer+, devopsplan, feature, ~"group::team planning" -
#13149 Make dropdown filters consistent across the app ~"Category::Project Management", UX, devopsplan, feature, ~"filter bar", ~"group::team planning", ~"search" -
#13148 (closed) Introduce third "not-null" option for board filters ~"Category::Issue Boards", ~"Plan", UX, devopsplan, feature, ~"filter bar", ~"group::team planning" -
#13098 (closed) Show a "close issue" button at the sidebar on the issue board ~"Category::Issue Boards", devopsplan, feature, ~"group::team planning" -
#12805 (closed) Default swim lanes in issue boards + Copy from existing ~"Category::Issue Boards", Persona: Product Manager, UX, devopsplan, feature, ~"group::team planning" -
#12803 (closed) Project images should be served scaled. ~"Plan", devopsplan, feature, frontend, ~"group::team planning" -
#12789 (closed) Mass edit integration settings across all projects from Service Template (Jira specifically) ~"Jira", ~"Plan", devopsplan, ~"external services", feature, ~"group::team planning" -
#12785 (closed) Make epics more accessible/easier to find ~"Plan", UX, devopsplan, feature, ~"group::team planning" -
#12644 (closed) Add comments and see related MRs on board issue detail sidebar ~"Plan", devopsplan, feature, ~"group::team planning" -
#12522 (closed) Service Desk - complete mail, when opening a new ticket ~"Plan", devopsplan, feature, ~"group::team planning" -
#12435 Add attribute to specify an issue template while creating an issue via API ~"Plan", api, devopsplan, feature, ~"group::team planning", issues -
#12285 (closed) Allow glob filtering of scoped labels ~"Plan", devopsplan, feature, ~"group::team planning", internal customer, labels -
#12243 (closed) Not possible to hide requester's e-mail when making Service Desk issues public ~"Category::Service Desk", ~"Plan", auto updated, devopsplan, feature, ~"group::team planning", issues -
#12194 (closed) Showing progress more accurately in burndown chart ~"Plan", burndown/up charts, devopsplan, feature, ~"group::team planning" -
#11819 Separate progress bar / percentage for MRs in a milestone ~"Plan", UX, backend, devopsplan, feature, frontend, ~"group::team planning", milestones
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
| ~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
|---|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 1 | 0 | 0 | 0 |
| ~P3 | 0 | 1 | 9 | 5 | 0 |
| ~P4 | 0 | 0 | 3 | 4 | 0 |
| ~"No priority" | 0 | 0 | 0 | 0 | 3 |
Unscheduled frontend ~bug (non-customer)
-
#13099 (closed) No weight number on zero-weight issue ~"Category::Issue Boards", ~"bug", devopsplan, frontend, ~"group::team planning", issue weight
Unscheduled ~bug (non-customer)
-
#13254 (closed) Issue relative position scope in group boards does not include projects in subgroups ~"Category::Issue Boards", ~"Plan", ~"bug", devopsplan, ~"group::team planning" -
#13229 (closed) /assignquick command fails if user is already assigned ~"bug", devopscreate, ~"group::team planning"
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:
Edited by Donald Cook