2019-07-30 - Triage report for "group::analytics"
Hi, @valexieva @dennis @lmcandrew
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
-
#4527 dashboard displaying analytics across all projects ~"Manage", UX, admin dashboard, analytics, customer, ~"cycle analytics", devopsmanage, feature, ~"group::analytics" -
#1035 (closed) Instance wide analytics CS Top 10 (2018CQ2), ~"Manage", analytics, customer, devopsmanage, feature, ~"group::analytics" -
#112 (closed) Code analytics ~"Accepting merge requests", CS Top 10 (2018CQ2), GitLab Premium, ~"Manage", Product Vision FY20, analytics, auto updated, backend, customer, devopsmanage, direction, feature, frontend, ~"group::analytics", meta, potential proposal, product work
Unscheduled feature (non-customer)
-
#12821 (closed) Simple and Scalable Dashboards ~"Manage", UX, analytics, ~"cycle analytics", devopsmanage, feature, ~"group::analytics" -
#12635 (closed) New - to be reused ~"Category::Value Stream Management", GitLab Ultimate, UX, analytics, backend, devopsmanage, feature, frontend, ~"group::analytics" -
#10663 (closed) Value stream analytics - Two label events for cycle time ~"Accepting merge requests", ~"Category::Value Stream Management", GitLab Ultimate, ~"Manage", backend, devopsmanage, direction, feature, frontend, ~"group::analytics", internal customer -
#8203 Show individual file history in code analytics GitLab Ultimate, ~"Manage", UX, backend, devopsmanage, feature, frontend, ~"group::analytics"
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 | 1 | 0 | 0 |
| ~P2 | 0 | 1 | 0 | 0 | 0 |
| ~P3 | 0 | 0 | 0 | 0 | 0 |
| ~P4 | 0 | 0 | 0 | 0 | 0 |
| ~"No priority" | 0 | 0 | 1 | 0 | 4 |
Unscheduled ~bug (non-customer)
-
#12400 (closed) Repository import fails with "Cannot modify association" ~"Manage", ~"bug", devopsmanage, ~"group::analytics", ~"import" -
#12127 (closed) Activity displays wrong names after migration ~"Manage", ~"bug", devopsmanage, ~"group::analytics", ~"project export", ~"project import" -
#12107 (closed) Project export fails due to statement timeout ~"bug", devopsmanage, ~"group::analytics", ~"performance", ~"project export" -
#11408 (closed) absolute links fail when importing project from gh-pages ~"Manage", ~"S3", ~"bug", devopsmanage, ~"group::analytics", ~"import", ~"pages"
Heatmap for ~missed-SLO bugs
| ~S1 | ~S2 | ~S3 | ~S4 | |
|---|---|---|---|---|
| ~P1 | 0 | 0 | 1 | 0 |
| ~P2 | 0 | 1 | 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: